Physical downlink control channel transmissions for multicast/broadcast system services

ABSTRACT

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may monitor a search space associated with a physical downlink control channel (PDCCH) corresponding to a multicast/broadcast (MBS) physical downlink shared channel (PDSCH) for at least one MBS PDCCH communication having a payload that is scrambled according to a PDCCH payload scrambling sequence based on a value of a radio network temporary identifier (RNTI), wherein the value of the RNTI is equal to a group-RNTI (G-RNTI) or zero. The UE may receive the at least one MBS PDCCH communication. Numerous other aspects are described.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application claims priority to U.S. Provisional PatentApplication No. 63/260,560, filed on Aug. 25, 2021, entitled “PHYSICALDOWNLINK CONTROL CHANNEL TRANSMISSIONS FOR MULTICAST/BROADCAST SYSTEMSERVICES” and also claims priority to U.S. Provisional PatentApplication No. 63/262,349, filed on Oct. 10, 2021, entitled “PHYSICALDOWNLINK CONTROL CHANNEL TRANSMISSIONS FOR MULTICAST/BROADCAST SYSTEMSERVICES.” Both applications are assigned to the assignee hereof. Thedisclosures of the prior applications are considered part of and areincorporated by reference into this patent application.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wirelesscommunication and to techniques and apparatuses for physical downlinkcontrol channel transmissions for multicast/broadcast system services.

BACKGROUND

Wireless communication systems are widely deployed to provide varioustelecommunication services such as telephony, video, data, messaging,and broadcasts. Typical wireless communication systems may employmultiple-access technologies capable of supporting communication withmultiple users by sharing available system resources (e.g., bandwidth,transmit power, or the like). Examples of such multiple-accesstechnologies include code division multiple access (CDMA) systems, timedivision multiple access (TDMA) systems, frequency division multipleaccess (FDMA) systems, orthogonal frequency division multiple access(OFDMA) systems, single-carrier frequency division multiple access(SC-FDMA) systems, time division synchronous code division multipleaccess (TD-SCDMA) systems, and Long Term Evolution (LTE).LTE/LTE-Advanced is a set of enhancements to the Universal MobileTelecommunications System (UMTS) mobile standard promulgated by theThird Generation Partnership Project (3GPP).

A wireless network may include one or more network nodes that supportcommunication for a user equipment (UE) or multiple UEs. A UE maycommunicate with a network node via downlink communications and uplinkcommunications. “Downlink” (or “DL”) refers to a communication link fromthe network node to the UE, and “uplink” (or “UL”) refers to acommunication link from the UE to the network node.

The above multiple access technologies have been adopted in varioustelecommunication standards to provide a common protocol that enablesdifferent UEs to communicate on a municipal, national, regional, and/orglobal level. New Radio (NR), which may be referred to as 5G, is a setof enhancements to the LTE mobile standard promulgated by the 3GPP. NRis designed to better support mobile broadband internet access byimproving spectral efficiency, lowering costs, improving services,making use of new spectrum, and better integrating with other openstandards using orthogonal frequency division multiplexing (OFDM) with acyclic prefix (CP) (CP-OFDM) on the downlink, using CP-OFDM and/orsingle-carrier frequency division multiplexing (SC-FDM) (also known asdiscrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink, aswell as supporting beamforming, multiple-input multiple-output (MIMO)antenna technology, and carrier aggregation. As the demand for mobilebroadband access continues to increase, further improvements in LTE, NR,and other radio access technologies remain useful.

SUMMARY

Some aspects described herein relate to a method of wirelesscommunication performed by a user equipment (UE). The method may includemonitoring a search space associated with a physical downlink controlchannel (PDCCH) corresponding to a multicast/broadcast system (MBS)physical downlink shared channel (PDSCH) for at least one MBS PDCCHcommunication having a payload that is scrambled according to a PDCCHpayload scrambling sequence based on a value of a radio networktemporary identifier (RNTI), wherein the value of the RNTI is equal tozero. The method may include receiving the at least one MBS PDCCHcommunication.

Some aspects described herein relate to a method of wirelesscommunication performed by a UE. The method may include monitoring asearch space associated with a PDCCH corresponding to an MBS PDSCH forat least one MBS PDCCH communication having a control channel element(CCE) index corresponding to a hash function that is based on a value ofan RNTI, wherein the value of the RNTI is equal to zero. The method mayinclude receiving the at least one MBS PDCCH communication.

Some aspects described herein relate to a method of wirelesscommunication performed by a UE. The method may include receiving an MBSconfiguration that configures a plurality of G-RNTIs for a cell. Themethod may include monitoring, based on the MBS configuration, at leastone search space associated with a PDCCHPDCCH corresponding to an MBSPDSCH of the cell for at least one MBS PDCCH communication thatschedules at least one MBS PDSCH communication of a plurality of MBSPDSCH communications.

Some aspects described herein relate to a method of wirelesscommunication performed by a network node. The method may includetransmitting an MBS configuration that indicates a PDCCH payloadscrambling sequence based on a value of an RNTI for a search spaceassociated with a PDCCHPDCCH corresponding to an MBS PDSCH, wherein thevalue of the RNTI is equal to zero. The method may include transmittingat least one MBS PDCCH communication based at least in part on theconfiguration.

Some aspects described herein relate to a method of wirelesscommunication performed by a base station. The method may includetransmitting an MBS configuration that indicates a PDCCH hash functionbased on a value of an RNTI for a search space associated with a PDCCHcorresponding to an MBS PDSCH, wherein the value of the RNTI is equal tozero. The method may include transmitting at least one MBS PDCCHcommunication based at least in part on the configuration.

Some aspects described herein relate to a method of wirelesscommunication performed by a network node. The method may includetransmitting an MBS configuration that configures a plurality of G-RNTIsfor a cell. The method may include transmitting, based on the MBSconfiguration and using at least one search space associated with aPDCCH corresponding to an MBS PDSCH of the cell, at least one MBS PDCCHcommunication that schedules at least one MBS PDSCH communication of aplurality of MBS PDSCH communications.

Some aspects described herein relate to a UE for wireless communication.The user equipment may include a memory and one or more processorscoupled to the memory. The one or more processors may be configured tomonitor a search space associated with a PDCCH corresponding to an MBSPDSCH for at least one MBS PDCCH communication having a payload that isscrambled according to a PDCCH payload scrambling sequence based on avalue of an RNTI, wherein the value of the RNTI is equal to zero. Theone or more processors may be configured to receive the at least one MBSPDCCH communication.

Some aspects described herein relate to a UE for wireless communication.The user equipment may include a memory and one or more processorscoupled to the memory. The one or more processors may be configured tomonitor a search space associated with a PDCCH corresponding to an MBSPDSCH for at least one MBS PDCCH communication having a CCE indexcorresponding to a hash function that is based on a value of an RNTI,wherein the value of the RNTI is equal to zero. The one or moreprocessors may be configured to receive the at least one MBS PDCCHcommunication.

Some aspects described herein relate to a UE for wireless communication.The user equipment may include a memory and one or more processorscoupled to the memory. The one or more processors may be configured toreceive an MBS configuration that configures a plurality of G-RNTIs fora cell. The one or more processors may be configured to monitor, basedon the MBS configuration, at least one search space associated with aPDCCH corresponding to an MBS PDSCH of the cell for at least one MBSPDCCH communication that schedules at least one MBS PDSCH communicationof a plurality of MBS PDSCH communications.

Some aspects described herein relate to a network node for wirelesscommunication. The network node may include a memory and one or moreprocessors coupled to the memory. The one or more processors may beconfigured to transmit an MBS configuration that indicates a PDCCHpayload scrambling sequence based on a value of an RNTI for a searchspace associated with a PDCCH corresponding to an MBS PDSCH, wherein thevalue of the RNTI is equal to a G-RNTI or zero. The one or moreprocessors may be configured to transmit at least one MBS PDCCHcommunication based at least in part on the configuration.

Some aspects described herein relate to a network node for wirelesscommunication. The network node may include a memory and one or moreprocessors coupled to the memory. The one or more processors may beconfigured to transmit an MB S configuration that indicates a PDCCH hashfunction based on a value of an RNTI for a search space associated witha PDCCH corresponding to an MBS PDSCH, wherein the value of the RNTI isequal to zero. The one or more processors may be configured to transmitat least one MBS PDCCH communication based at least in part on theconfiguration.

Some aspects described herein relate to a network node for wirelesscommunication. The network node may include a memory and one or moreprocessors coupled to the memory. The one or more processors may beconfigured to transmit an MB S configuration that configures a pluralityof G-RNTIs for a cell. The one or more processors may be configured totransmit, based on the MBS configuration and using at least one searchspace associated with a PDCCH corresponding to an MBS PDSCH of the cell,at least one MBS PDCCH communication that schedules at least one MB SPDSCH communication of a plurality of MBS PDSCH communications.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a UE. The set of instructions, when executed by one ormore processors of the UE, may cause the UE to monitor a search spaceassociated with a PDCCH corresponding to an MBS PDSCH for at least oneMBS PDCCH communication having a payload that is scrambled according toa PDCCH payload scrambling sequence based on a value of an RNTI, whereinthe value of the RNTI is equal to zero. The set of instructions, whenexecuted by one or more processors of the UE, may cause the UE toreceive the at least one MBS PDCCH communication.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a UE. The set of instructions, when executed by one ormore processors of the UE, may cause the UE to monitor a search spaceassociated with a PDCCH corresponding to an MBS PDSCH for at least oneMBS PDCCH communication having a CCE index corresponding to a hashfunction that is based on a value of an RNTI, wherein the value of theRNTI is equal to zero. The set of instructions, when executed by one ormore processors of the UE, may cause the UE to receive the at least oneMBS PDCCH communication.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by an UE. The set of instructions, when executed by one ormore processors of the UE, may cause the UE to receive an MBSconfiguration that configures a plurality of G-RNTIs for a cell. The setof instructions, when executed by one or more processors of the UE, maycause the UE to monitor, based on the MBS configuration, at least onesearch space associated with a PDCCH corresponding to an MBS PDSCH ofthe cell for at least one MBS PDCCH communication that schedules atleast one MBS PDSCH communication of a plurality of MBS PDSCHcommunications.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a network node. The set of instructions, when executedby one or more processors of the network node, may cause the networknode to transmit an MBS configuration that indicates a PDCCH payloadscrambling sequence based on a value of an RNTI for a search spaceassociated with a PDCCH corresponding to an MBS PDSCH, wherein the valueof the RNTI is equal to zero. The set of instructions, when executed byone or more processors of the network node, may cause the network nodeto transmit at least one MBS PDCCH communication based at least in parton the configuration.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a network node. The set of instructions, when executedby one or more processors of the network node, may cause the networknode to transmit an MBS configuration that indicates a PDCCH hashfunction based on a value of an RNTI for a search space associated witha PDCCH corresponding to an MBS PDSCH, wherein the value of the RNTI isequal to zero. The set of instructions, when executed by one or moreprocessors of the network node, may cause the network node to transmitat least one MBS PDCCH communication based at least in part on theconfiguration.

Some aspects described herein relate to a non-transitorycomputer-readable medium that stores a set of instructions for wirelesscommunication by a network node. The set of instructions, when executedby one or more processors of the network node, may cause the networknode to transmit an MBS configuration that configures a plurality ofG-RNTIs for a cell. The set of instructions, when executed by one ormore processors of the network node, may cause the network node totransmit, based on the MBS configuration and using at least one searchspace associated with a PDCCH corresponding to an MBS PDSCH of the cell,at least one MBS PDCCH communication that schedules at least one MBSPDSCH communication of a plurality of MBS PDSCH communications.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for monitoring a searchspace associated with a PDCCH corresponding to an MBS PDSCH for at leastone MBS PDCCH communication having a payload that is scrambled accordingto a PDCCH payload scrambling sequence based on a value of an RNTI,wherein the value of the RNTI is equal to zero. The apparatus mayinclude means for receiving the at least one MBS PDCCH communication.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for monitoring a searchspace associated with a PDCCH corresponding to an MBS PDSCH for at leastone MBS PDCCH communication having a CCE index corresponding to a hashfunction that is based on a value of an RNTI, wherein the value of theRNTI is equal to zero. The apparatus may include means for receiving theat least one MBS PDCCH communication.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for receiving an MBSconfiguration that configures a plurality of G-RNTIs for a cell. Theapparatus may include means for monitoring, based on the MBSconfiguration, at least one search space associated with a PDCCHcorresponding to an MBS PDSCH of the cell for at least one MBS PDCCHcommunication that schedules at least one MBS PDSCH communication of aplurality of MBS PDSCH communications.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for transmitting an MBSconfiguration that indicates a PDCCH payload scrambling sequence basedon a value of an RNTI for a search space associated with a PDCCHcorresponding to an MB S PDSCH, wherein the value of the RNTI is equalto zero. The apparatus may include means for transmitting at least oneMBS PDCCH communication based at least in part on the configuration.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for transmitting an MBSconfiguration that indicates a PDCCH hash function based on a value ofam RNTI for a search space associated with a PDCCH corresponding to anMBS PDSCH, wherein the value of the RNTI is equal to zero. The apparatusmay include means for transmitting at least one MBS PDCCH communicationbased at least in part on the configuration.

Some aspects described herein relate to an apparatus for wirelesscommunication. The apparatus may include means for transmitting an MBSconfiguration that configures a plurality of G-RNTIs for a cell. Theapparatus may include means for transmitting, based on the MBSconfiguration and using at least one search space associated with aPDCCH corresponding to an MBS PDSCH of the cell, at least one MBS PDCCHcommunication that schedules at least one MBS PDSCH communication of aplurality of MBS PDSCH communications.

Aspects generally include a method, apparatus, system, computer programproduct, non-transitory computer-readable medium, user equipment, basestation, network node, wireless communication device, and/or processingsystem as substantially described herein with reference to and asillustrated by the drawings and specification.

The foregoing has outlined rather broadly the features and technicaladvantages of examples according to the disclosure in order that thedetailed description that follows may be better understood. Additionalfeatures and advantages will be described hereinafter. The conceptionand specific examples disclosed may be readily utilized as a basis formodifying or designing other structures for carrying out the samepurposes of the present disclosure. Such equivalent constructions do notdepart from the scope of the appended claims. Characteristics of theconcepts disclosed herein, both their organization and method ofoperation, together with associated advantages, will be betterunderstood from the following description when considered in connectionwith the accompanying figures. Each of the figures is provided for thepurposes of illustration and description, and not as a definition of thelimits of the claims.

While aspects are described in the present disclosure by illustration tosome examples, those skilled in the art will understand that suchaspects may be implemented in many different arrangements and scenarios.Techniques described herein may be implemented using different platformtypes, devices, systems, shapes, sizes, and/or packaging arrangements.For example, some aspects may be implemented via integrated chipembodiments or other non-module-component based devices (e.g., end-userdevices, vehicles, communication devices, computing devices, industrialequipment, retail/purchasing devices, medical devices, and/or artificialintelligence devices). Aspects may be implemented in chip-levelcomponents, modular components, non-modular components, non-chip-levelcomponents, device-level components, and/or system-level components.Devices incorporating described aspects and features may includeadditional components and features for implementation and practice ofclaimed and described aspects. For example, transmission and receptionof wireless signals may include one or more components for analog anddigital purposes (e.g., hardware components including antennas, radiofrequency (RF) chains, power amplifiers, modulators, buffers,processors, interleavers, adders, and/or summers). It is intended thataspects described herein may be practiced in a wide variety of devices,components, systems, distributed arrangements, and/or end-user devicesof varying size, shape, and constitution.

BRIEF DESCRIPTION OF THE DRAWINGS

So that the above-recited features of the present disclosure can beunderstood in detail, a more particular description, briefly summarizedabove, may be had by reference to aspects, some of which are illustratedin the appended drawings. It is to be noted, however, that the appendeddrawings illustrate only certain typical aspects of this disclosure andare therefore not to be considered limiting of its scope, for thedescription may admit to other equally effective aspects. The samereference numbers in different drawings may identify the same or similarelements.

FIG. 1 is a diagram illustrating an example of a wireless network, inaccordance with the present disclosure.

FIG. 2 is a diagram illustrating an example of a base station incommunication with a user equipment (UE) in a wireless network, inaccordance with the present disclosure.

FIG. 3 is a diagram illustrating an example of a disaggregated basedstation architecture, in accordance with the present disclosure.

FIG. 4 is a diagram illustrating an example associated with physicaldownlink control channel (PDCCH) transmissions for multicast/broadcastsystem (MB S) services, in accordance with the present disclosure.

FIGS. 5-10 are diagrams illustrating example processes associated withPDCCH transmissions for MBS services, in accordance with the presentdisclosure.

FIGS. 11 and 12 are diagrams of example apparatuses for wirelesscommunication, in accordance with the present disclosure.

DETAILED DESCRIPTION

Various aspects of the disclosure are described more fully hereinafterwith reference to the accompanying drawings. This disclosure may,however, be embodied in many different forms and should not be construedas limited to any specific structure or function presented throughoutthis disclosure. Rather, these aspects are provided so that thisdisclosure will be thorough and complete, and will fully convey thescope of the disclosure to those skilled in the art. One skilled in theart should appreciate that the scope of the disclosure is intended tocover any aspect of the disclosure disclosed herein, whether implementedindependently of or combined with any other aspect of the disclosure.For example, an apparatus may be implemented or a method may bepracticed using any number of the aspects set forth herein. In addition,the scope of the disclosure is intended to cover such an apparatus ormethod which is practiced using other structure, functionality, orstructure and functionality in addition to or other than the variousaspects of the disclosure set forth herein. It should be understood thatany aspect of the disclosure disclosed herein may be embodied by one ormore elements of a claim.

Several aspects of telecommunication systems will now be presented withreference to various apparatuses and techniques. These apparatuses andtechniques will be described in the following detailed description andillustrated in the accompanying drawings by various blocks, modules,components, circuits, steps, processes, algorithms, or the like(collectively referred to as “elements”). These elements may beimplemented using hardware, software, or combinations thereof. Whethersuch elements are implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem.

While aspects may be described herein using terminology commonlyassociated with a 5G or New Radio (NR) radio access technology (RAT),aspects of the present disclosure can be applied to other RATs, such asa 3G RAT, a 4G RAT, and/or a RAT subsequent to 5G (e.g., 6G).

FIG. 1 is a diagram illustrating an example of a wireless network 100,in accordance with the present disclosure. The wireless network 100 maybe or may include elements of a 5G (e.g., NR) network and/or a 4G (e.g.,Long Term Evolution (LTE)) network, among other examples. The wirelessnetwork 100 may include one or more base stations 110 (shown as a BS 110a, a BS 110 b, a BS 110 c, and a BS 110 d), a user equipment (UE) 120 ormultiple UEs 120 (shown as a UE 120 a, a UE 120 b, a UE 120 c, a UE 120d, and a UE 120 e), and/or other network entities. A base station 110 isan entity that communicates with UEs 120. A base station 110 (sometimesreferred to as a BS) may include, for example, an NR base station, anLTE base station, a Node B, an eNB (e.g., in 4G), a gNB (e.g., in 5G),an access point, and/or a transmission reception point (TRP). Each basestation 110 may provide communication coverage for a particulargeographic area. In the Third Generation Partnership Project (3GPP), theterm “cell” can refer to a coverage area of a base station 110 and/or abase station subsystem serving this coverage area, depending on thecontext in which the term is used.

A base station 110 may provide communication coverage for a macro cell,a pico cell, a femto cell, and/or another type of cell. A macro cell maycover a relatively large geographic area (e.g., several kilometers inradius) and may allow unrestricted access by UEs 120 with servicesubscriptions. A pico cell may cover a relatively small geographic areaand may allow unrestricted access by UEs 120 with service subscription.A femto cell may cover a relatively small geographic area (e.g., a home)and may allow restricted access by UEs 120 having association with thefemto cell (e.g., UEs 120 in a closed subscriber group (CSG)). A basestation 110 for a macro cell may be referred to as a macro base station.A base station 110 for a pico cell may be referred to as a pico basestation. A base station 110 for a femto cell may be referred to as afemto base station or an in-home base station. In the example shown inFIG. 1 , the BS 110 a may be a macro base station for a macro cell 102a, the BS 110 b may be a pico base station for a pico cell 102 b, andthe BS 110 c may be a femto base station for a femto cell 102 c. A basestation may support one or multiple (e.g., three) cells.

In some examples, a cell may not necessarily be stationary, and thegeographic area of the cell may move according to the location of a basestation 110 that is mobile (e.g., a mobile base station). In someexamples, the base stations 110 may be interconnected to one anotherand/or to one or more other base stations 110 or network nodes (notshown) in the wireless network 100 through various types of backhaulinterfaces, such as a direct physical connection or a virtual network,using any suitable transport network.

The wireless network 100 may include one or more relay stations. A relaystation is an entity that can receive a transmission of data from anupstream station (e.g., a base station 110 or a UE 120) and send atransmission of the data to a downstream station (e.g., a UE 120 or abase station 110). A relay station may be a UE 120 that can relaytransmissions for other UEs 120. In the example shown in FIG. 1 , the BS110 d (e.g., a relay base station) may communicate with the BS 110 a(e.g., a macro base station) and the UE 120 d in order to facilitatecommunication between the BS 110 a and the UE 120 d. A base station 110that relays communications may be referred to as a relay station, arelay base station, a relay, or the like.

In some aspects, the term “base station” or “network entity” may referto an aggregated base station, a disaggregated base station, anintegrated access and backhaul (IAB) node, a relay node, or one or morecomponents thereof. For example, in some aspects, “base station” or“network entity” may refer to a CU, a DU, an RU, a Near-Real Time(Near-RT) RAN Intelligent Controller (RIC), or a Non-Real Time (Non-RT)MC, or a combination thereof. In some aspects, the term “base station”or “network entity” may refer to one device configured to perform one ormore functions, such as those described herein in connection with thenetwork entity 110. In some aspects, the term “base station” or “networkentity” may refer to a plurality of devices configured to perform theone or more functions. For example, in some distributed systems, each ofa quantity of different devices (which may be located in the samegeographic location or in different geographic locations) may beconfigured to perform at least a portion of a function, or to duplicateperformance of at least a portion of the function, and the term “basestation” or “network entity” may refer to any one or more of thosedifferent devices. In some aspects, the term “base station” or “networkentity” may refer to one or more virtual base stations or one or morevirtual base station functions. For example, in some aspects, two ormore base station functions may be instantiated on a single device. Insome aspects, the term “base station” or “network entity” may refer toone of the base station functions and not another. In this way, a singledevice may include more than one base station.

The wireless network 100 may be a heterogeneous network that includesbase stations 110 of different types, such as macro base stations, picobase stations, femto base stations, relay base stations, or the like.These different types of base stations 110 may have different transmitpower levels, different coverage areas, and/or different impacts oninterference in the wireless network 100. For example, macro basestations may have a high transmit power level (e.g., 5 to 40 watts)whereas pico base stations, femto base stations, and relay base stationsmay have lower transmit power levels (e.g., 0.1 to 2 watts).

A network controller 130 may couple to or communicate with a set of basestations 110 and may provide coordination and control for these basestations 110. The network controller 130 may communicate with the basestations 110 via a backhaul communication link. The base stations 110may communicate with one another directly or indirectly via a wirelessor wireline backhaul communication link.

The UEs 120 may be dispersed throughout the wireless network 100, andeach UE 120 may be stationary or mobile. A UE 120 may include, forexample, an access terminal, a terminal, a mobile station, and/or asubscriber unit. A UE 120 may be a cellular phone (e.g., a smart phone),a personal digital assistant (PDA), a wireless modem, a wirelesscommunication device, a handheld device, a laptop computer, a cordlessphone, a wireless local loop (WLL) station, a tablet, a camera, a gamingdevice, a netbook, a smartbook, an ultrabook, a medical device, abiometric device, a wearable device (e.g., a smart watch, smartclothing, smart glasses, a smart wristband, smart jewelry (e.g., a smartring or a smart bracelet)), an entertainment device (e.g., a musicdevice, a video device, and/or a satellite radio), a vehicular componentor sensor, a smart meter/sensor, industrial manufacturing equipment, aglobal positioning system device, and/or any other suitable device thatis configured to communicate via a wireless medium.

Some UEs 120 may be considered machine-type communication (MTC) orevolved or enhanced machine-type communication (eMTC) UEs. An MTC UEand/or an eMTC UE may include, for example, a robot, a drone, a remotedevice, a sensor, a meter, a monitor, and/or a location tag, that maycommunicate with a base station, another device (e.g., a remote device),or some other entity. Some UEs 120 may be considered Internet-of-Things(IoT) devices, and/or may be implemented as NB-IoT (narrowband IoT)devices. Some UEs 120 may be considered a Customer Premises Equipment. AUE 120 may be included inside a housing that houses components of the UE120, such as processor components and/or memory components. In someexamples, the processor components and the memory components may becoupled together. For example, the processor components (e.g., one ormore processors) and the memory components (e.g., a memory) may beoperatively coupled, communicatively coupled, electronically coupled,and/or electrically coupled.

In general, any number of wireless networks 100 may be deployed in agiven geographic area. Each wireless network 100 may support aparticular RAT and may operate on one or more frequencies. A RAT may bereferred to as a radio technology, an air interface, or the like. Afrequency may be referred to as a carrier, a frequency channel, or thelike. Each frequency may support a single RAT in a given geographic areain order to avoid interference between wireless networks of differentRATs. In some cases, NR or 5G RAT networks may be deployed.

In some examples, two or more UEs 120 (e.g., shown as UE 120 a and UE120 e) may communicate directly using one or more sidelink channels(e.g., without using a base station 110 as an intermediary tocommunicate with one another). For example, the UEs 120 may communicateusing peer-to-peer (P2P) communications, device-to-device (D2D)communications, a vehicle-to-everything (V2X) protocol (e.g., which mayinclude a vehicle-to-vehicle (V2V) protocol, a vehicle-to-infrastructure(V2I) protocol, or a vehicle-to-pedestrian (V2P) protocol), and/or amesh network. In such examples, a UE 120 may perform schedulingoperations, resource selection operations, and/or other operationsdescribed elsewhere herein as being performed by the base station 110.

Devices of the wireless network 100 may communicate using theelectromagnetic spectrum, which may be subdivided by frequency orwavelength into various classes, bands, channels, or the like. Forexample, devices of the wireless network 100 may communicate using oneor more operating bands. In 5G NR, two initial operating bands have beenidentified as frequency range designations FR1 (410 MHz-7.125 GHz) andFR2 (24.25 GHz-52.6 GHz). It should be understood that although aportion of FR1 is greater than 6 GHz, FR1 is often referred to(interchangeably) as a “Sub-6 GHz” band in various documents andarticles. A similar nomenclature issue sometimes occurs with regard toFR2, which is often referred to (interchangeably) as a “millimeter wave”band in documents and articles, despite being different from theextremely high frequency (EHF) band (30 GHz-300 GHz) which is identifiedby the International Telecommunications Union (ITU) as a “millimeterwave” band.

The frequencies between FR1 and FR2 are often referred to as mid-bandfrequencies. Recent 5G NR studies have identified an operating band forthese mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25 GHz). Frequency bands falling within FR3 may inherit FR1characteristics and/or FR2 characteristics, and thus may effectivelyextend features of FR1 and/or FR2 into mid-band frequencies. Inaddition, higher frequency bands are currently being explored to extend5G NR operation beyond 52.6 GHz. For example, three higher operatingbands have been identified as frequency range designations FR4a or FR4-1(52.6 GHz-71 GHz), FR4 (52.6 GHz-114.25 GHz), and FR5 (114.25 GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

With the above examples in mind, unless specifically stated otherwise,it should be understood that the term “sub-6 GHz” or the like, if usedherein, may broadly represent frequencies that may be less than 6 GHz,may be within FR1, or may include mid-band frequencies. Further, unlessspecifically stated otherwise, it should be understood that the term“millimeter wave” or the like, if used herein, may broadly representfrequencies that may include mid-band frequencies, may be within FR2,FR4, FR4-a or FR4-1, and/or FR5, or may be within the EHF band. It iscontemplated that the frequencies included in these operating bands(e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified,and techniques described herein are applicable to those modifiedfrequency ranges.

In some aspects, the UE 120 may include a communication manager 140. Asdescribed in more detail elsewhere herein, the communication manager 140may monitor a search space associated with a physical downlink controlchannel (PDCCH) corresponding to a multicast/broadcast system (MBS)physical downlink shared channel (PDSCH) for at least one MBS PDCCHcommunication having a payload that is scrambled according to a PDCCHpayload scrambling sequence based on a value of a radio networktemporary identifier (RNTI), wherein the value of the RNTI is equal to agroup-RNTI (G-RNTI) or zero; and receive the at least one MBS PDCCHcommunication. Additionally, or alternatively, the communication manager140 may perform one or more other operations described herein.

In some aspects, the UE 120 may include a communication manager 140. Asdescribed in more detail elsewhere herein, the communication manager 140may monitor a search space associated with a PDCCH corresponding to anMBS PDSCH for at least one MBS PDCCH communication having a controlchannel element (CCE) index corresponding to a hash function that isbased on a value of an RNTI, wherein the value of the RNTI is equal to aG-RNTI or zero; and receive the at least one MBS PDCCH communication.Additionally, or alternatively, the communication manager 140 mayperform one or more other operations described herein.

In some aspects, the UE 120 may include a communication manager 140. Asdescribed in more detail elsewhere herein, the communication manager 140may receive an MBS configuration that configures a plurality of G-RNTIsfor a cell; and monitor, based on the MBS configuration, at least onesearch space associated with a PDCCH corresponding to an MBS PDSCH ofthe cell for at least one MBS PDCCH communication that schedules atleast one MBS PDSCH communication of a plurality of MBS PDSCHcommunications. Additionally, or alternatively, the communicationmanager 140 may perform one or more other operations described herein.

In some aspects, the network node 110 may include a communicationmanager 150. As described in more detail elsewhere herein, thecommunication manager 150 may transmit an MBS configuration thatindicates a PDCCH payload scrambling sequence based on a value of anRNTI for a search space associated with a PDCCH corresponding to an MBSPDSCH, wherein the value of the RNTI is equal to a G-RNTI or zero; andtransmit at least one MBS PDCCH communication based at least in part onthe configuration. Additionally, or alternatively, the communicationmanager 150 may perform one or more other operations described herein.

In some aspects, the network node 110 may include a communicationmanager 150. As described in more detail elsewhere herein, thecommunication manager 150 may transmit an MBS configuration thatindicates a PDCCH hash function based on a value of an RNTI for a searchspace associated with a PDCCH corresponding to an MBS PDSCH, wherein thevalue of the RNTI is equal to a G-RNTI or zero; and transmit at leastone MBS PDCCH communication based at least in part on the configuration.Additionally, or alternatively, the communication manager 150 mayperform one or more other operations described herein.

In some aspects, the network node 110 may include a communicationmanager 150. As described in more detail elsewhere herein, thecommunication manager 150 may transmit an MBS configuration thatconfigures a plurality of G-RNTIs for a cell; and transmit, based on theMBS configuration and using at least one search space associated with aPDCCH corresponding to an MBS PDSCH of the cell, at least one MBS PDCCHcommunication that schedules at least one MBS PDSCH communication of aplurality of MBS PDSCH communications. Additionally, or alternatively,the communication manager 150 may perform one or more other operationsdescribed herein.

As indicated above, FIG. 1 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 1 .

FIG. 2 is a diagram illustrating an example 200 of a base station 110 incommunication with a UE 120 in a wireless network 100, in accordancewith the present disclosure. The base station 110 may be equipped with aset of antennas 234 a through 234 t, such as T antennas (T≥1). The UE120 may be equipped with a set of antennas 252 a through 252 r, such asR antennas (R≥1).

At the base station 110, a transmit processor 220 may receive data, froma data source 212, intended for the UE 120 (or a set of UEs 120). Thetransmit processor 220 may select one or more modulation and codingschemes (MCSs) for the UE 120 based at least in part on one or morechannel quality indicators (CQIs) received from that UE 120. The basestation 110 may process (e.g., encode and modulate) the data for the UE120 based at least in part on the MCS(s) selected for the UE 120 and mayprovide data symbols for the UE 120. The transmit processor 220 mayprocess system information (e.g., for semi-static resource partitioninginformation (SRPI)) and control information (e.g., CQI requests, grants,and/or upper layer signaling) and provide overhead symbols and controlsymbols. The transmit processor 220 may generate reference symbols forreference signals (e.g., a cell-specific reference signal (CRS) or ademodulation reference signal (DMRS)) and synchronization signals (e.g.,a primary synchronization signal (PSS) or a secondary synchronizationsignal (SSS)). A transmit (TX) multiple-input multiple-output (MIMO)processor 230 may perform spatial processing (e.g., precoding) on thedata symbols, the control symbols, the overhead symbols, and/or thereference symbols, if applicable, and may provide a set of output symbolstreams (e.g., T output symbol streams) to a corresponding set of modems232 (e.g., T modems), shown as modems 232 a through 232 t. For example,each output symbol stream may be provided to a modulator component(shown as MOD) of a modem 232. Each modem 232 may use a respectivemodulator component to process a respective output symbol stream (e.g.,for OFDM) to obtain an output sample stream. Each modem 232 may furtheruse a respective modulator component to process (e.g., convert toanalog, amplify, filter, and/or upconvert) the output sample stream toobtain a downlink signal. The modems 232 a through 232 t may transmit aset of downlink signals (e.g., T downlink signals) via a correspondingset of antennas 234 (e.g., T antennas), shown as antennas 234 a through234 t.

At the UE 120, a set of antennas 252 (shown as antennas 252 a through252 r) may receive the downlink signals from the base station 110 and/orother base stations 110 and may provide a set of received signals (e.g.,R received signals) to a set of modems 254 (e.g., R modems), shown asmodems 254 a through 254 r. For example, each received signal may beprovided to a demodulator component (shown as DEMOD) of a modem 254.Each modem 254 may use a respective demodulator component to condition(e.g., filter, amplify, downconvert, and/or digitize) a received signalto obtain input samples. Each modem 254 may use a demodulator componentto further process the input samples (e.g., for OFDM) to obtain receivedsymbols. A MIMO detector 256 may obtain received symbols from the modems254, may perform MIMO detection on the received symbols if applicable,and may provide detected symbols. A receive processor 258 may process(e.g., demodulate and decode) the detected symbols, may provide decodeddata for the UE 120 to a data sink 260, and may provide decoded controlinformation and system information to a controller/processor 280. Theterm “controller/processor” may refer to one or more controllers, one ormore processors, or a combination thereof. A channel processor maydetermine a reference signal received power (RSRP) parameter, a receivedsignal strength indicator (RSSI) parameter, a reference signal receivedquality (RSRQ) parameter, and/or a CQI parameter, among other examples.In some examples, one or more components of the UE 120 may be includedin a housing 284.

The network controller 130 may include a communication unit 294, acontroller/processor 290, and a memory 292. The network controller 130may include, for example, one or more devices in a core network. Thenetwork controller 130 may communicate with the base station 110 via thecommunication unit 294.

One or more antennas (e.g., antennas 234 a through 234 t and/or antennas252 a through 252 r) may include, or may be included within, one or moreantenna panels, one or more antenna groups, one or more sets of antennaelements, and/or one or more antenna arrays, among other examples. Anantenna panel, an antenna group, a set of antenna elements, and/or anantenna array may include one or more antenna elements (within a singlehousing or multiple housings), a set of coplanar antenna elements, a setof non-coplanar antenna elements, and/or one or more antenna elementscoupled to one or more transmission and/or reception components, such asone or more components of FIG. 2 .

On the uplink, at the UE 120, a transmit processor 264 may receive andprocess data from a data source 262 and control information (e.g., forreports that include RSRP, RSSI, RSRQ, and/or CQI) from thecontroller/processor 280. The transmit processor 264 may generatereference symbols for one or more reference signals. The symbols fromthe transmit processor 264 may be precoded by a TX MIMO processor 266 ifapplicable, further processed by the modems 254 (e.g., for DFT-s-OFDM orCP-OFDM), and transmitted to the base station 110. In some examples, themodem 254 of the UE 120 may include a modulator and a demodulator. Insome examples, the UE 120 includes a transceiver. The transceiver mayinclude any combination of the antenna(s) 252, the modem(s) 254, theMIMO detector 256, the receive processor 258, the transmit processor264, and/or the TX MIMO processor 266. The transceiver may be used by aprocessor (e.g., the controller/processor 280) and the memory 282 toperform aspects of any of the methods described herein (e.g., withreference to FIGS. 4-12 ).

At the base station 110, the uplink signals from UE 120 and/or other UEsmay be received by the antennas 234, processed by the modem 232 (e.g., ademodulator component, shown as DEMOD, of the modem 232), detected by aMIMO detector 236 if applicable, and further processed by a receiveprocessor 238 to obtain decoded data and control information sent by theUE 120. The receive processor 238 may provide the decoded data to a datasink 239 and provide the decoded control information to thecontroller/processor 240. The base station 110 may include acommunication unit 244 and may communicate with the network controller130 via the communication unit 244. The base station 110 may include ascheduler 246 to schedule one or more UEs 120 for downlink and/or uplinkcommunications. In some examples, the modem 232 of the base station 110may include a modulator and a demodulator. In some examples, the basestation 110 includes a transceiver. The transceiver may include anycombination of the antenna(s) 234, the modem(s) 232, the MIMO detector236, the receive processor 238, the transmit processor 220, and/or theTX MIMO processor 230. The transceiver may be used by a processor (e.g.,the controller/processor 240) and the memory 242 to perform aspects ofany of the methods described herein (e.g., with reference to FIGS. 4-12).

The controller/processor 240 of the base station 110, thecontroller/processor 280 of the UE 120, and/or any other component(s) ofFIG. 2 may perform one or more techniques associated with PDCCHtransmissions for MBS services, as described in more detail elsewhereherein. For example, the controller/processor 240 of the base station110, the controller/processor 280 of the UE 120, and/or any othercomponent(s) of FIG. 2 may perform or direct operations of, for example,process 500 of FIG. 5 , process 600 of FIG. 6 , process 700 of FIG. 7 ,process 800 of FIG. 8 , process 900 of FIG. 9 , process 1000 of FIG. 10, and/or other processes as described herein. The memory 242 and thememory 282 may store data and program codes for the base station 110 andthe UE 120, respectively. In some examples, the memory 242 and/or thememory 282 may include a non-transitory computer-readable medium storingone or more instructions (e.g., code and/or program code) for wirelesscommunication. For example, the one or more instructions, when executed(e.g., directly, or after compiling, converting, and/or interpreting) byone or more processors of the base station 110 and/or the UE 120, maycause the one or more processors, the UE 120, and/or the base station110 to perform or direct operations of, for example, process 500 of FIG.5 , process 600 of FIG. 6 , process 700 of FIG. 7 , process 800 of FIG.8 , process 900 of FIG. 9 , process 1000 of FIG. 10 , and/or otherprocesses as described herein. In some examples, executing instructionsmay include running the instructions, converting the instructions,compiling the instructions, and/or interpreting the instructions, amongother examples.

In some aspects, the UE includes means for monitoring a search spaceassociated with a PDCCH corresponding to an MBS PDSCH for at least oneMBS PDCCH communication having a payload that is scrambled according toa PDCCH payload scrambling sequence based on a value of an RNTI, whereinthe value of the RNTI is equal to a G-RNTI or zero; and/or means forreceiving the at least one MBS PDCCH communication. The means for the UEto perform operations described herein may include, for example, one ormore of communication manager 140, antenna 252, modem 254, MIMO detector256, receive processor 258, transmit processor 264, TX MIMO processor266, controller/processor 280, or memory 282.

In some aspects, the UE includes means for monitoring a search spaceassociated with a PDCCH corresponding to an MBS PDSCH for at least oneMBS PDCCH communication having a CCE index corresponding to a hashfunction that is based on a value of an RNTI, wherein the value of theRNTI is equal to a G-RNTI or zero; and/or means for receiving the atleast one MBS PDCCH communication. The means for the UE to performoperations described herein may include, for example, one or more ofcommunication manager 140, antenna 252, modem 254, MIMO detector 256,receive processor 258, transmit processor 264, TX MIMO processor 266,controller/processor 280, or memory 282.

In some aspects, the UE includes means for receiving an MBSconfiguration that configures a plurality of G-RNTIs for a cell; and/ormeans for monitoring, based on the MBS configuration, at least onesearch space associated with a PDCCH corresponding to an MBS PDSCH ofthe cell for at least one MBS PDCCH communication that schedules atleast one MBS PDSCH communication of a plurality of MBS PDSCHcommunications. The means for the UE to perform operations describedherein may include, for example, one or more of communication manager140, antenna 252, modem 254, MIMO detector 256, receive processor 258,transmit processor 264, TX MIMO processor 266, controller/processor 280,or memory 282.

In some aspects, the network node includes means for transmitting an MBSconfiguration that indicates a PDCCH payload scrambling sequence basedon a value of an RNTI for a search space associated with a PDCCHcorresponding to an MB S PDSCH, wherein the value of the RNTI is equalto a G-RNTI or zero; and/or means for transmitting at least one MBSPDCCH communication based at least in part on the configuration. Themeans for the network node to perform operations described herein mayinclude, for example, one or more of communication manager 150, transmitprocessor 220, TX MIMO processor 230, modem 232, antenna 234, MIMOdetector 236, receive processor 238, controller/processor 240, memory242, or scheduler 246.

In some aspects, the network node includes means for transmitting an MBSconfiguration that indicates a PDCCH hash function based on a value ofan RNTI for a search space associated with a PDCCH corresponding to anMBS PDSCH, wherein the value of the RNTI is equal to a G-RNTI or zero;and/or means for transmitting at least one MBS PDCCH communication basedat least in part on the configuration. The means for the network node toperform operations described herein may include, for example, one ormore of communication manager 150, transmit processor 220, TX MIMOprocessor 230, modem 232, antenna 234, MIMO detector 236, receiveprocessor 238, controller/processor 240, memory 242, or scheduler 246.

In some aspects, the network node includes means for transmitting an MBSconfiguration that configures a plurality of G-RNTIs for a cell; and/ormeans for transmitting, based on the MBS configuration and using atleast one search space associated with a PDCCH corresponding to an MBSPDSCH of the cell, at least one MBS PDCCH communication that schedulesat least one MBS PDSCH communication of a plurality of MBS PDSCHcommunications. The means for the network node to perform operationsdescribed herein may include, for example, one or more of communicationmanager 150, transmit processor 220, TX MIMO processor 230, modem 232,antenna 234, MIMO detector 236, receive processor 238,controller/processor 240, memory 242, or scheduler 246.

While blocks in FIG. 2 are illustrated as distinct components, thefunctions described above with respect to the blocks may be implementedin a single hardware, software, or combination component or in variouscombinations of components. For example, the functions described withrespect to the transmit processor 264, the receive processor 258, and/orthe TX MIMO processor 266 may be performed by or under the control ofthe controller/processor 280.

As indicated above, FIG. 2 is provided as an example. Other examples maydiffer from what is described with regard to FIG. 2 .

Deployment of communication systems, such as 5G NR systems, may bearranged in multiple manners with various components or constituentparts. In a 5G NR system, or network, a network node, a network entity,a mobility element of a network, a RAN node, a core network node, anetwork element, a base station, or a network equipment may beimplemented in an aggregated or disaggregated architecture. For example,a base station (such as a Node B (NB), an evolved NB (eNB), an NR BS, a5G NB, an access point (AP), a TRP, or a cell, among other examples), orone or more units (or one or more components) performing base stationfunctionality, may be implemented as an aggregated base station (alsoknown as a standalone base station or a monolithic base station) or adisaggregated base station.

An aggregated base station may be configured to utilize a radio protocolstack that is physically or logically integrated within a single RANnode (for example, within a single device or unit). A disaggregated basestation may be configured to utilize a protocol stack that is physicallyor logically distributed among two or more units (such as a CU, one ormore DUs, or one or more RUs). In some examples, a CU may be implementedwithin a RAN node, and one or more DUs may be co-located with the CU, oralternatively, may be geographically or virtually distributed throughoutone or multiple other RAN nodes. The DUs may be implemented tocommunicate with one or more RUs. Each of the CU, DU and RU also can beimplemented as virtual units, such as a virtual central unit (VCU), avirtual distributed unit (VDU), or a virtual radio unit (VRU), amongother examples.

Base station-type operation or network design may consider aggregationcharacteristics of base station functionality. For example,disaggregated base stations may be utilized in an IAB network, an openradio access network (O-RAN (such as the network configuration sponsoredby the O-RAN Alliance)), or a virtualized radio access network (vRAN,also known as a cloud radio access network (C-RAN)) to facilitatescaling of communication systems by separating base stationfunctionality into one or more units that can be individually deployed.A disaggregated base station may include functionality implementedacross two or more units at various physical locations, as well asfunctionality implemented for at least one unit virtually, which canenable flexibility in network design. The various units of thedisaggregated base station can be configured for wired or wirelesscommunication with at least one other unit of the disaggregated basestation.

FIG. 3 is a diagram illustrating an example disaggregated base stationarchitecture 300, in accordance with the present disclosure. Thedisaggregated base station architecture 300 may include a CU 310 thatcan communicate directly with a core network 320 via a backhaul link, orindirectly with the core network 320 through one or more disaggregatedcontrol units (such as a Near-RT RIC 325 via an E2 link, or a Non-RT RIC315 associated with a Service Management and Orchestration (SMO)Framework 305, or both). A CU 310 may communicate with one or more DUs330 via respective midhaul links, such as through F1 interfaces. Each ofthe DUs 330 may communicate with one or more RUs 340 via respectivefronthaul links. Each of the RUs 340 may communicate with one or moreUEs 120 via respective radio frequency (RF) access links. In someimplementations, a UE 120 may be simultaneously served by multiple RUs340.

Each of the units, including the CUs 310, the DUs 330, the RUs 340, aswell as the Near-RT RICs 325, the Non-RT RICs 315, and the SMO Framework305, may include one or more interfaces or be coupled with one or moreinterfaces configured to receive or transmit signals, data, orinformation (collectively, signals) via a wired or wireless transmissionmedium. Each of the units, or an associated processor or controllerproviding instructions to one or multiple communication interfaces ofthe respective unit, can be configured to communicate with one or moreof the other units via the transmission medium. In some examples, eachof the units can include a wired interface, configured to receive ortransmit signals over a wired transmission medium to one or more of theother units, and a wireless interface, which may include a receiver, atransmitter or transceiver (such as a RF transceiver), configured toreceive or transmit signals, or both, over a wireless transmissionmedium to one or more of the other units.

In some aspects, the CU 310 may host one or more higher layer controlfunctions. Such control functions can include radio resource control(RRC) functions, packet data convergence protocol (PDCP) functions, orservice data adaptation protocol (SDAP) functions, among other examples.Each control function can be implemented with an interface configured tocommunicate signals with other control functions hosted by the CU 310.The CU 310 may be configured to handle user plane functionality (forexample, Central Unit—User Plane (CU-UP) functionality), control planefunctionality (for example, Central Unit—Control Plane (CU-CP)functionality), or a combination thereof. In some implementations, theCU 310 can be logically split into one or more CU-UP units and one ormore CU-CP units. A CU-UP unit can communicate bidirectionally with aCU-CP unit via an interface, such as the E1 interface when implementedin an O-RAN configuration. The CU 310 can be implemented to communicatewith a DU 330, as necessary, for network control and signaling.

Each DU 330 may correspond to a logical unit that includes one or morebase station functions to control the operation of one or more RUs 340.In some aspects, the DU 330 may host one or more of a radio link control(RLC) layer, a MAC layer, and one or more high physical (PHY) layersdepending, at least in part, on a functional split, such as a functionalsplit defined by the 3GPP. In some aspects, the one or more high PHYlayers may be implemented by one or more modules for forward errorcorrection (FEC) encoding and decoding, scrambling, and modulation anddemodulation, among other examples. In some aspects, the DU 330 mayfurther host one or more low PHY layers, such as implemented by one ormore modules for a fast Fourier transform (FFT), an inverse FFT (iFFT),digital beamforming, or physical random access channel (PRACH)extraction and filtering, among other examples. Each layer (which alsomay be referred to as a module) can be implemented with an interfaceconfigured to communicate signals with other layers (and modules) hostedby the DU 330, or with the control functions hosted by the CU 310.

Each RU 340 may implement lower-layer functionality. In somedeployments, an RU 340, controlled by a DU 330, may correspond to alogical node that hosts RF processing functions or low-PHY layerfunctions, such as performing an FFT, performing an iFFT, digitalbeamforming, or PRACH extraction and filtering, among other examples,based on a functional split (for example, a functional split defined bythe 3GPP), such as a lower layer functional split. In such anarchitecture, each RU 340 can be operated to handle over the air (OTA)communication with one or more UEs 120. In some implementations,real-time and non-real-time aspects of control and user planecommunication with the RU(s) 340 can be controlled by the correspondingDU 330. In some scenarios, this configuration can enable each DU 330 andthe CU 310 to be implemented in a cloud-based RAN architecture, such asa vRAN architecture.

The SMO Framework 305 may be configured to support RAN deployment andprovisioning of non-virtualized and virtualized network elements. Fornon-virtualized network elements, the SMO Framework 305 may beconfigured to support the deployment of dedicated physical resources forRAN coverage requirements, which may be managed via an operations andmaintenance interface (such as an O1 interface). For virtualized networkelements, the SMO Framework 305 may be configured to interact with acloud computing platform (such as an open cloud (O-Cloud) platform 390)to perform network element life cycle management (such as to instantiatevirtualized network elements) via a cloud computing platform interface(such as an O2 interface). Such virtualized network elements caninclude, but are not limited to, CUs 310, DUs 330, RUs 340, non-RT RICs315, and Near-RT RICs 325. In some implementations, the SMO Framework305 can communicate with a hardware aspect of a 4G RAN, such as an openeNB (O-eNB) 311, via an O1 interface. Additionally, in someimplementations, the SMO Framework 305 can communicate directly witheach of one or more RUs 340 via a respective O1 interface. The SMOFramework 305 also may include a Non-RT RIC 315 configured to supportfunctionality of the SMO Framework 305.

The Non-RT RIC 315 may be configured to include a logical function thatenables non-real-time control and optimization of RAN elements andresources, Artificial Intelligence/Machine Learning (AI/ML) workflowsincluding model training and updates, or policy-based guidance ofapplications/features in the Near-RT RIC 325. The Non-RT RIC 315 may becoupled to or communicate with (such as via an A1 interface) the Near-RTRIC 325. The Near-RT RIC 325 may be configured to include a logicalfunction that enables near-real-time control and optimization of RANelements and resources via data collection and actions over an interface(such as via an E2 interface) connecting one or more CUs 310, one ormore DUs 330, or both, as well as an O-eNB, with the Near-RT RIC 325.

In some implementations, to generate AI/ML models to be deployed in theNear-RT RIC 325, the Non-RT RIC 315 may receive parameters or externalenrichment information from external servers. Such information may beutilized by the Near-RT RIC 325 and may be received at the SMO Framework305 or the Non-RT RIC 315 from non-network data sources or from networkfunctions. In some examples, the Non-RT RIC 315 or the Near-RT RIC 325may be configured to tune RAN behavior or performance. For example, theNon-RT RIC 315 may monitor long-term trends and patterns for performanceand employ AI/ML models to perform corrective actions through the SMOFramework 305 (such as reconfiguration via an O1 interface) or viacreation of RAN management policies (such as A1 interface policies).

A network node may use PDCCH transmissions to schedule PDSCHtransmissions for a UE. However, a number of UEs may be interacting witha cell and/or connected to the cell. To facilitate directing a PDCCHtransmission to a specific UE of multiple UEs in a cell, a network nodecan scramble a PDCCH payload prior to modulation in accordance with ascrambling sequence that is recognizable by the UE. In this way, UEs towhich the transmission is not directed can avoid decoding a schedulingtransmission, and the network node can schedule each UE independently,even though more than one UE may detect the scheduling transmission.

In some cases, a UE may be configured to monitor for PDCCH transmissionshaving payloads scrambled according to a scrambling sequence that isbased on a value of an RNTI, where the value of the RNTI is equal to acell-RNTI (C-RNTI) or zero. In some cases, for example, the value of theRNTI is equal to the C-RNTI if the communication is intended for aUE-specific search space (USS) and if a particular parameter isconfigured, and equal to zero otherwise.

For example, a UE may be configured to monitor for PDCCH transmissionsthat have a payload containing a block of scrambled bits {tilde over(b)}(0), . . . {tilde over (b)} (M_(bit)−1) generated by a scramblingoperation performed on a block of bits b(0), . . . b(M_(bit)−1) prior tomodulation according to {tilde over (b)}(i)=(b(i)+c(i))mod2, where thescrambling sequence c(i) may be specified in a wireless communicationstandard. The scrambling sequence generator can be initialized with ascrambling sequence initialization functionc _(init)=(n _(RNTI)·2¹⁶ +n _(ID))mod2³¹where, for a UE-specific search space, n_(ID)∈ {0,1, . . . ,65535}equals the higher-layer parameter pdcch-DMRS-ScramblingID if configured,and n_(ID)=n_(ID) ^(cell) otherwise, and where n_(RNTI) is given by theC-RNTI for a PDCCH in a UE-specific search space if the higher-layerparameter pdcch-DMRS-ScramblingID is configured, and n_(RNTI)=0otherwise.

The PDCCH payload scrambling above is useful for directing PDCCHtransmissions to a UE among multiple UEs. However, in an MBS system, anattempt by the network node to use this scrambling scheme will not besuccessful in directing a PDCCH transmission to multiple UEs (e.g., formulticast and/or broadcast), as the C-RNTIs are UE-specific. As aresult, the scrambling scheme may inhibit MB S communications andthereby have a negative impact on network performance.

In some cases, for common search spaces (CSSs), multiple UEs can monitora PDCCH candidate on a same set of CCEs. For example, for a search spaceset s associated with a core resource set (CORESET) p, the CCE indexesfor aggregation level L corresponding to a PDCCH candidate m_(s,n) _(Cl)of the search space set in slot n_(s,f) ^(μ) for an active downlinkbandwidth part (BWP) of a serving cell corresponding to carrierindicator field value n_(Cl) can be given by

$\begin{matrix}{{L \cdot \left\{ {\left( {Y_{p,n_{s,f}^{\mu}} + \left\lfloor \frac{m_{s,n_{CI}} \cdot N_{{CCE},p}}{L \cdot M_{s,\max}^{(L)}} \right\rfloor + n_{CI}} \right){mod}\left\lfloor \frac{N_{{CCE},p}}{L} \right\rfloor} \right\}} + i} & \end{matrix}$where for any CSS, Y_(p,n) _(s,f) _(μ) =0; for any USS, Y_(p,n) _(s,f)_(μ) =(A_(p)·Y_(p,n) _(s,f) _(μ) ⁻¹) modD, Y_(p,−1)=n_(RNTI)≠0,A_(p)=39827 for pmod3=0, A_(p)=39829 for pmod3=1, A_(p)=39839 forpmod3=2, and D=65537; i=0, . . . , L−1; N_(CCE,p) is the number of CCEs,numbered from 0 to N_(CCE,p)−1, in CORESET p and, if any, per resourceblock (RB) set; n_(Cl) is the carrier indicator field value if the UE isconfigured with a carrier indicator field by a cross carrier schedulingconfiguration parameter (e.g., CrossCarrierScheduhngConfig) for theserving cell on which PDCCH is monitored; otherwise, including for anyCSS, n_(Cl)=0; m_(s,n) _(Cl) =0, . . . , M_(s,n) _(Cl) ^((L))−1, whereM_(s,n) _(Cl) ^((L)) is the number of PDCCH candidates the UE isconfigured to monitor for aggregation level L of a search space set sfor a serving cell corresponding to n_(Cl); for any CSS, M_(s,max)^((L))=M_(s,0) ^((L)); for a USS, M_(s,max) ^((L)) is the maximum ofM_(s,n) _(Cl) ^((L)) over all configured n_(Cl) values for a CCEaggregation level L of search space set s; and the RNTI value used forn_(RNTI) is the C-RNTI.

In this way, a single downlink control information (DCI) transmissioncan be delivered to all the UEs. For UE-specific search spaces,different UEs have different C-RNTI values and a PDCCH candidate fordifferent UEs can be mapped on different set of CCEs. However, ingeneral, common DCI transmission on a UE-specific search space is notpossible. Thus, in an MBS system, an attempt by the network node to usea hash function based on a C-RNTI will not be successful in directing aPDCCH transmission to multiple UEs (e.g., for multicast and/orbroadcast), as the C-RNTIs are UE-specific. As a result, the hashfunction may inhibit MBS communications and thereby have a negativeimpact on network performance.

In some cases, error detection can be provided on DCI transmissionsusing a cyclic redundancy check (CRC). To facilitate a CRC, an entirepayload may be used to calculate CRC parity bits according to aprocedure that can be specified by a wireless standard. The CRC paritybits can be scrambled with a corresponding RNTI such that a UE caninterpret the CRC parity bits for detecting errors. The RNTI on whichthe CRC scrambling can be based can be any number of different RNTIs,including a C-RNTI, a modulation coding scheme cell RNTI (MCS-C-RNTI), aconfigured scheduling RNTI (CS-RNTI), a system information RNTI(SI-RNTI), a paging RNTI (P-RNTI), a random access RNTI (RA-RNTI),and/or a slot format indication RNTI (SFI-RNTI), among other examples.Although a G-RNTI may be used to scramble CRC parity bits, a singleG-RNTI may not enable multiple PDSCH transmissions for multiple MBSservices. As a result, the CRC scrambling using a single RNTI mayinhibit MBS communications and thereby have a negative impact on networkperformance.

In some cases, a search space associated with a PDCCH corresponding toan MBS PDSCH may include, for example, a CSS of an MBS-dedicated type(which may be referred to, for example, as a Type-x CSS). The searchspace may be used for group-common PDCCH transmissions for multicast inan RRC connected state. The monitoring priority of search spaceassociated with a PDCCH corresponding to an MBS PDSCH can be determinedbased on the search space set indexes of the Type-x CSS set and USSsets, regardless of which DCI format of group-common PDCCH is configuredin the Type-x CSS. The group-common PDCCH used in an MBS can beconfigured to support at least two DCI formats. For example, DCI format1_0 can be used as the baseline for the first DCI format with CRCscrambled with G-RNTI. The DCI format 1_1 or 1_2 can be used as thebaseline for the second DCI format with CRC scrambled with G-RNTI. Asdescribed above, however, USS-based payload scrambling schemes, hashfunctions, and/or CRC scrambling schemes may be unable to accommodatethe MBS communications.

Some aspects may provide PDCCH payload scrambling for PDCCHtransmissions that schedule MBS PDSCH communications. Some aspects mayprovide hash functions for PDCCH transmissions that schedule MBS PDSCHcommunications. Some aspects may provide CRC scrambling for PDCCHtransmissions that schedule MBS PDSCH communications. The scrambling andhashing techniques described herein may be based on RNTIs that may havevalues equal to zero or equal to a G-RNTI (or G-RNTIs). In this way,PDCCH payload scrambling, hash functions, and CRC scrambling may beadapted to be used for PDCCH transmissions that schedule MBS PDSCHcommunications so that multiple UEs may receive multicast and/orbroadcast transmissions. As a result, some aspects may facilitatemulticast and/or broadcast transmissions, thereby having a positiveimpact on network performance.

FIG. 4 is a diagram illustrating an example 400 associated with PDCCHtransmissions for MBS services, in accordance with the presentdisclosure. As shown in FIG. 4 , a network node 402 and a UE 404 maycommunicate with one another. The network node 402 may communicate witha number of UEs 404 in an MBS implementation, though only one of suchUEs 404 is shown in FIG. 4 .

As shown by reference number 406, the network node 402 may transmit, andthe UE 404 may receive, an MBS configuration. In some aspects, forexample, the UE 404 may be provided with a common frequency resource(CFR) configuration. The CFR may include information indicating where,in a frequency domain, MBS data may be scheduled. The CFR configurationmay include other parameters used to facilitate MBS communications. Forexample, RRC configurations for the CORESET and the associated searchspace may be provided as part of the CFR configuration.

In some aspects, the MBS configuration (and/or one or more aspectsthereof) may be, include, be included in, or be similar to the CFRconfiguration. In some aspects, the network node 402 may transmit, andthe UE 404 may receive, a configuration of a PDCCH DMRS scramblingidentifier for a control resource set associated with the search space.For example, the configuration may configure the pdcch-DMRS-ScramblingIDparameter. In some aspects, the network node 402 may transmit, and theUE 404 may receive, a dedicated configuration indication that configuresthe search space associated with a PDCCH corresponding to an MBS PDSCH.The dedicated configuration indication may be transmitted using adedicated RRC message and/or a dedicated RRC parameter. In some aspects,the network node 402 may transmit, and the UE 404 may receive, an MBSconfiguration that configures a plurality of G-RNTIs for a cell. In someaspects, at least one G-RNTI of the plurality of G-RNTIs may include avalue of an RNTI associated with at least one of a PDCCH payloadscrambling sequence, a hash function corresponding to a CCE index, or aCRC scrambling sequence. In some aspects, the G-RNTIs may be configuredusing a G-RNTI list. In some aspects, the configuration may indicate amapping between the G-RNTIs and respective multicast services. Themulticast services may include specified multicast service identifiers(IDs). In some aspects, the network node 402 may transmit, and the UE404 may receive, a configuration that indicates a configurable dedicatedvalue of an RNTI. The configurable dedicated value of the RNTI may beassociated with at least one of a PDCCH payload scrambling sequence, ahash function corresponding to a CCE index, or a CRC scramblingsequence. In some aspects, the network node 402 may transmit, and the UE120 may receive, an RRC configuration that indicates a mapping betweenat least one search space and at least one G-RNTI of the plurality ofG-RNTIs. Any of the configurations described above may be included in aCFR configuration and/or an MBS configuration, among other examples.

As shown by reference number 408, the network node 402 may generate anMBS PDCCH communication using a scrambling sequence, a hash function,and/or a CRC sequence, among other examples, as described herein. Asshown by reference number 410, the UE 404 may monitor a search space forat least one MBS PDCCH communication.

For example, in some aspects, the UE 404 may monitor a search spaceassociated with a PDCCH corresponding to an MBS PDSCH for at least oneMBS PDCCH communication having a payload that is scrambled according toa PDCCH payload scrambling sequence based on a value of an RNTI. Thevalue of the RNTI may be equal to a G-RNTI or zero. The value of theRNTI may be equal to zero, and the UE 404 may receive a configuration ofa PDCCH DMRS scrambling ID for a CORESET associated with the searchspace. In some aspects, the UE 404 does not receive a configuration of aPDCCH DMRS scrambling ID for a CORESET associated with the search space.For example, payload scrambling for PDCCH scheduling MBS PDSCH may bebased on n_(RNTI)=0. This may be the case regardless of whether apdcch-DMRS-ScramblingID parameter is provided for a controlResourceSetfor a CORESET associated with the search space. In some aspects, thevalue of the RNTI is equal to zero, and a PDCCH DMRS scrambling ID isnot supported for a CORESET associated with the search space. Forexample, the payload scrambling for PDCCH scheduling MBS PDSCH may bebased on n_(RNTI)=0 and pdcch-DMRS-ScramblingID may not be supported forthe controlResourceSet for a CORESET associated with the search space.

In some aspects, the value of the RNTI may be equal to the G-RNTI, andthe UE 404 may receive a configuration of a PDCCH DMRS scrambling ID fora CORESET associated with the search space. The value of the RNTI may beequal to the G-RNTI, and the UE 404 may not receive a configuration of aPDCCH DMRS scrambling ID for a CORESET associated with the search space.For example, payload scrambling for PDCCH scheduling MBS PDSCH may bebased on n_(RNTI)=G-RNTI regardless of whether or notpdcch-DMRS-ScramblingID is provided for the controlResourceSet for aCORESET associated with the search space.

In some aspects, the network node 402 may transmit, and the UE 404 mayreceive a configuration of a PDCCH DMRS scrambling ID for a CORESETassociated with the search space, and the value of the RNTI may be equalto the G-RNTI based on the network node 402 transmitting and/or the UE404 receiving the configuration of the PDCCH DMRS scrambling ID. In someaspects, the UE 404 may not receive a configuration of a PDCCH DMRSscrambling ID for a CORESET associated with the search space, and thevalue of the RNTI may be equal to zero based on the network node 402 nottransmitting and/or the UE 404 not receiving the configuration of thePDCCH DMRS scrambling ID. For example, payload scrambling for PDCCHscheduling MBS PDSCH may be based on n_(RNTI)=G-RNTI ifpdcch-DMRS-ScramblingID is provided for the controlResourceSet for theCORESET associated with the search space and based on n_(RNTI)=0otherwise.

In some aspects, the network node 402 may transmit, and the UE 404 mayreceive a configuration of a PDCCH DMRS scrambling ID for a CORESETassociated with the search space; and the network node 402 may transmit,and the UE 404 may receive, a dedicated configuration indication thatconfigures the search space. The value of the RNTI may be equal to theG-RNTI based on the network node 402 transmitting and/or the UE 404receiving the configuration of the PDCCH DMRS scrambling ID and thededicated configuration indication. In some aspects, the network node402 may transmit, and the UE 404 may receive, the dedicatedconfiguration indication by transmitting and receiving, respectively, adedicated RRC message and/or RRC parameter. The value of the RNTI may beequal to zero based on a determination that the network node 402 has nottransmitted and/or the UE 404 has not received, a configuration of aPDCCH DMRS scrambling ID for a CORESET associated with the search spaceand a dedicated configuration indication that configures the searchspace. For example, payload scrambling for PDCCH scheduling MBS PDSCHmay be based on n_(RNTI)=G-RNTI if pdcch-DMRS-ScramblingID is providedfor the controlResourceSet for the CORESET associated with the searchspace and if the search space is configured by UE-dedicated RRC message(or configured with dedicated RRC parameter), and based on n_(RNTI)=0otherwise.

In some aspects, the network node 402 may transmit, and the UE 404 mayreceive a configuration of a PDCCH DMRS scrambling ID for a CORESETassociated with the search space, and the UE 404 may monitor the searchspace by monitoring the search space only in a an RRC connected state.The value of the RNTI may be equal to the G-RNTI based on receiving theconfiguration of the PDCCH DMRS scrambling ID and monitoring the searchspace only in the RRC connected state. The value of the RNTI may beequal to zero based on a determination that the network node 402 has nottransmitted and/or the UE 404 has not received, a configuration of aPDCCH DMRS scrambling ID for a CORESET associated with the search spaceand a determination that the search space is not monitored only in anRRC connected state. For example, payload scrambling for PDCCHscheduling MBS PDSCH may be based on n_(RNTI)=G-RNTI ifpdcch-DMRS-ScramblingID is provided for the controlResourceSet for aCORESET associated with the search space and if the search space is theone monitored only in RRC_connected state, and based on n n_(RNTI)=0otherwise.

In some aspects, the at least one MBS PDCCH communication may include aDCI transmission that schedules an MBS PDSCH. The value of the RNTI maybe equal to zero based on a determination that a DCI format of the DCItransmission is a DCI format 1_0 and the value of the RNTI may be equalto the G-RNTI based on a determination that a DCI format of the DCItransmission is not a DCI format 1_0 (e.g., where the DCI transmissionformat is a DCI format 1_1 or 1_2). For example, payload scrambling forPDCCH scheduling MBS PDSCH may be based on n_(RNTI)=0 if the PDCCHscheduling MBS PDSCH is a DCI format 1_0 and based on n_(RNTI)=G-RNTIotherwise.

In some aspects, the UE 404 may monitor a search space for at least oneMBS PDCCH communication having a CCE index corresponding to a hashfunction that is based on a value of an RNTI, where the value of theRNTI is equal to a G-RNTI or zero. In some aspects, the value of theRNTI is equal to zero. For example, the hash function for the searchspace may be based on n_(RNTI)=0. In some aspects, the value of the RNTImay be equal to the G-RNTI. For example, the hash function for thesearch space may be based on n_(RNTI)=G-RNTI.

In some aspects, the network node 402 may transmit, and the UE 404 mayreceive an indication of an RRC parameter that enables the RNTI to equalthe G-RNTI, and the value of the RNTI may be equal to the G-RNTI basedon the network node 402 transmitting and/or the UE 404 receiving theindication of the RRC parameter. The value of the RNTI may be equal tozero based on a determination that the network node 402 has nottransmitted and/or the UE 404 has not received, an indication of an RRCparameter that enables the RNTI to equal the G-RNTI. For example, a hashfunction for the search space may be based on n_(RNTI)=G-RNTI if the UEis configured with a RRC parameter enabling n_(RNTI)=G-RNTI. The hashfunction may be based on n_(RNTI)=0 if the UE is not configured with aRRC parameter enabling n_(RNTI)=G-RNTI.

In some aspects, the network node 402 may transmit, and the UE 404 mayreceive a dedicated configuration indication that configures the searchspace, and the value of the RNTI may be equal to the G-RNTI based on thenetwork node 402 transmitting and/or the UE 404 receiving, the dedicatedconfiguration indication. In some aspects, the network node 402 maytransmit, and the UE 404 may receive, the dedicated configurationindication by transmitting and receiving, respectively, a dedicated RRCmessage and/or a dedicated RRC parameter. The value of the RNTI may beequal to zero based on a determination that the network node 402 has nottransmitted and/or that the UE 404 has not received, a dedicatedconfiguration indication that configures the search space. For example,in some aspects, the hash function for the search space may be based onn_(RNTI)=G-RNTI if the Type-x CSS is configured by UE-dedicated RRCmessage (or configured with dedicated RRC parameter) and based onn_(RNTI)=0 otherwise.

In some aspects, the UE 404 may monitor the search space by monitoringthe search space only in an RRC connected state, and the value of theRNTI may be equal to the G-RNTI based on the UE 404 monitoring thesearch space only in the RRC connected state. In some aspects, the valueof the RNTI may be equal to zero based on a determination that thesearch space is not monitored only in an RRC connected state. Forexample, the hash function for the search space may be based onn_(RNTI)=G-RNTI if the search space is the one monitored only inRRC_connected state and based on n_(RNTI)=0 otherwise.

In some aspects, as described above in connection with the scramblingsequence, for the hash function, the at least one MBS PDCCHcommunication may include a DCI transmission that schedules an MBSphysical downlink shared channel and the value of the RNTI may be equalto zero based on a determination that a DCI format of the DCItransmission is a DCI format 1_0. The value of the RNTI may be equal tothe G-RNTI based on a determination that a DCI format of the DCItransmission is not a DCI format 1_0.

In some aspects, for a downlink cell, the UE 404 may monitor PDCCH forMBS PDSCHs with multiple G-RNTIs. The network node 402 may transmit, andthe UE 404 may receive, an MBS configuration that configures a pluralityof G-RNTIs for a cell and the UE 404 may monitor, based on the MBSconfiguration, at least one search space of the cell for at least oneMBS PDCCH communication that schedules at least one MBS PDSCHcommunication of a plurality of MBS PDSCH communications. Each MBS PDSCHcommunication of the plurality of MBS PDSCH communications may beassociated with a respective G-RNTI of the plurality of G-RNTIs. Forexample, different G-RNTIs may be used for different multicast services.At least one G-RNTI of the plurality of G-RNTIs may include a value ofan RNTI associated with at least one of a PDCCH payload scramblingsequence, a hash function corresponding to a CCE index, or a CRCscrambling sequence.

In some aspects, for example, different G-RNTIs may be used forscrambling, hash functions, and/or CRC scrambling for DCIs for MBSPDSCHs associated with different G-RNTIs. In some aspects, the value ofthe RNTI may be equal to the at least one G-RNTI and at least oneadditional value of the RNTI may be equal to at least one additionalG-RNTI of the plurality of G-RNTIs. The value of the RNTI may be equalto the G-RNTI and at least one additional payload may be scrambledaccording to the PDCCH payload scrambling sequence based on at least oneadditional value of the RNTI, where the at least one additional value ofthe RNTI is equal to at least one additional G-RNTI of the plurality ofG-RNTIs. In some aspects, the value of the RNTI may be equal to theG-RNTI and at least one additional CCE index may correspond to at leastone additional hash function that is based on at least one additionalvalue of the RNTI, where the at least one additional value of the RNTIis equal to at least one additional G-RNTI of the plurality of G-RNTIs.

In some aspects, one RNTI value may be used for scrambling, hashfunction, and/or CRC scrambling for DCIs for MBS PDSCHs associated withdifferent G-RNTIs. For example, in some aspects, at least one additionalvalue of the RNTI may be equal to the value of the RNTI. At least oneadditional payload may be scrambled according to the PDCCH payloadscrambling sequence based on at least one additional value of the RNTI,where the at least one additional value of the RNTI is equal to thevalue of the RNTI. At least one additional hash function may be based onat least one additional value of the RNTI, where the at least oneadditional value of the RNTI is equal to the value of the RNTI.

In some aspects, the value of the RNTI may be equal to a specifiedG-RNTI of the plurality of G-RNTIs. For example, the RNTI may be equalto a lowest value among the plurality of G-RNTIs and/or a highest valueamong the plurality of G-RNTIs, among other examples. In some aspects,the RNTI may be equal to a specified G-RNTI of a G-RNTI list. Forexample, the plurality of G-RNTIs may be configured using a G-RNTI listand the value of the RNTI may be equal to a first listed G-RNTI of theG-RNTI list and/or a last listed G-RNTI of the G-RNTI list, among otherexamples. In some aspects, the G-RNTI may be mapped to a particularmulticast service (e.g., multicast service having the lowest multicastservice ID and/or the highest multicast service ID, among otherexamples).

In some aspects, the RNTI may have a value that is separatelyconfigurable. In some aspects, the value may be separately configurablespecifically for the hash function. In some aspects, the network node402 may transmit, and the UE 404 may receive a configuration thatindicates a configurable dedicated value of an RNTI. The configurablededicated value of the RNTI may be associated with at least one of aPDCCH payload scrambling sequence, a hash function corresponding to aCCE index, or a CRC scrambling sequence. In some aspects, for example,multicast UEs may be configured with a value for n_(RNTI) forscrambling, hash function, and/or CRC scrambling for DCIs for MBS PDSCHsassociated with different G-RNTIs. The multicast service may include aspecified multicast service ID of a plurality of multicast service IDs.In some aspects, the value of the RNTI may include a configurablededicated value.

In some aspects, where the at least one MBS PDCCH communication includesa plurality of MBS PDCCH communications, PDCCHs for MBS PDSCHsassociated with different G-RNTIs may be monitored on the same searchspace set. In some aspects, for example, the mapping from G-RNTI to thesearch space may be one to one. In some aspects, PDCCHs for MBS PDSCHsassociated with different G-RNTIs may be monitored on different searchspace sets. For example, the mapping from G-RNTI to the search space maybe many to one. In some aspects, the mapping between a G-RNTI and asearch space associated with a PDCCH corresponding to an MBS PDSCH maybe configured by RRC signaling. For example, the network node 402 maytransmit, and the UE 404 may receive, an RRC configuration thatindicates a mapping between at least one search space and at least oneG-RNTI of the plurality of G-RNTIs.

As shown by reference number 412, the network node 402 may transmit, andthe UE 404 may receive, the at least one MBS PDCCH communication.

As indicated above, FIG. 4 is provided as an example. Other examples maydiffer from what is described with respect to FIG. 4 .

FIG. 5 is a diagram illustrating an example process 500 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 500 is an example where the UE (e.g., UE 404) performsoperations associated with PDCCH transmissions for MBS services.

As shown in FIG. 5 , in some aspects, process 500 may include monitoringa search space associated with a PDCCH corresponding to an MBS PDSCH forat least one MBS PDCCH communication having a payload that is scrambledaccording to a PDCCH payload scrambling sequence based on a value of anRNTI, wherein the value of the RNTI is equal to a G-RNTI or zero (block510). For example, the UE (e.g., using communication manager 140 and/orreception component 1102, depicted in FIG. 11 ) may monitor a searchspace for at least one MBS PDCCH communication having a payload that isscrambled according to a PDCCH payload scrambling sequence based on avalue of an RNTI, wherein the value of the RNTI is equal to a G-RNTI orzero, as described above.

As further shown in FIG. 5 , in some aspects, process 500 may includereceiving the at least one MBS PDCCH communication (block 520). Forexample, the UE (e.g., using communication manager 140 and/or receptioncomponent 1102, depicted in FIG. 11 ) may receive the at least one MBSPDCCH communication, as described above.

Process 500 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, the value of the RNTI is equal to zero, the methodfurther comprising receiving a configuration of a PDCCH DMRS scramblingID for a CORSET associated with the search space.

In a second aspect, the value of the RNTI is equal to zero, and whereinthe UE does not receive a configuration of a PDCCH DMRS scrambling IDfor a CORESET associated with the search space.

In a third aspect, the value of the RNTI is equal to zero, and a PDCCHDMRS scrambling ID is not supported for a control resource setassociated with the search space.

In a fourth aspect, the value of the RNTI is equal to the G-RNTI, themethod further comprising receiving a configuration of a PDCCH DMRSscrambling ID for a CORESET associated with the search space.

In a fifth aspect, the value of the RNTI is equal to the G-RNTI, andwherein the UE does not receive a configuration of a PDCCH DMRSscrambling ID for a CORESET associated with the search space.

In a sixth aspect, process 500 includes receiving a configuration of aPDCCH DMRS scrambling ID for a CORESET associated with the search space,wherein the value of the RNTI is equal to the G-RNTI based on receivingthe configuration of the PDCCH DMRS scrambling ID.

In a seventh aspect, the UE does not receive a configuration of a PDCCHDMRS scrambling ID for a CORESET associated with the search space, andwherein the value of the RNTI is equal to zero based on the UE notreceiving the configuration of the PDCCH DMRS scrambling ID.

In an eighth aspect, process 500 includes receiving a configuration of aPDCCH DMRS scrambling ID for a CORESET associated with the search spaceand receiving a dedicated configuration indication that configures thesearch space, wherein the value of the RNTI is equal to the G-RNTI basedon receiving the configuration of the PDCCH DMRS scrambling ID and thededicated configuration indication.

In a ninth aspect, alone or in combination with the eighth aspect,receiving the dedicated configuration indication comprises receiving adedicated RRC message.

In a tenth aspect, alone or in combination with one or more of theeighth through ninth aspects, receiving the dedicated configurationindication comprises receiving an RRC message that indicates a dedicatedparameter.

In an eleventh aspect, the value of the RNTI is equal to zero based on adetermination that the UE has not received a configuration of a PDCCHDMRS scrambling ID for a CORESET associated with the search space and adedicated configuration indication that configures the search space.

In a twelfth aspect, process 500 includes receiving a configuration of aPDCCH DMRS scrambling ID for a CORESET associated with the search space,wherein monitoring the search space comprises monitoring the searchspace only in an RRC connected state, and wherein the value of the RNTIis equal to the G-RNTI based on receiving the configuration of the PDCCHDMRS scrambling ID and monitoring the search space only in the RRCconnected state.

In a thirteenth aspect, alone or in combination with one or more of thefirst through twelfth aspects, the value of the RNTI is equal to zerobased on a determination that the UE has not received a configuration ofa PDCCH DMRS scrambling ID for a CORESET associated with the searchspace and a determination that the search space is not monitored only ina radio resource control connected state.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, the at least one MBS PDCCHcommunication comprises a DCI transmission that schedules an MBS PDSCH.

In a fifteenth aspect, alone or in combination with the fourteenthaspect, the value of the RNTI is equal to zero based on a determinationthat a DCI format of the DCI transmission is a DCI format 1_0.

In a sixteenth aspect, alone or in combination with the fifteenthaspect, the value of the RNTI is equal to the G-RNTI based on adetermination that a DCI format of the DCI transmission is not a DCIformat 1_0.

In a seventeenth aspect, alone or in combination with one or more of thefirst through sixteenth aspects, the at least one MBS PDCCHcommunication schedules a plurality of MBS PDSCH communications, whereineach MBS PDSCH communication of the plurality of MBS PDSCHcommunications is associated with a respective G-RNTI of a plurality ofG-RNTIs that includes the G-RNTI.

In an eighteenth aspect, alone or in combination with the seventeenthaspect, the value of the RNTI is equal to the G-RNTI and wherein atleast one additional payload is scrambled according to the PDCCH payloadscrambling sequence based on at least one additional value of the RNTI,wherein the at least one additional value of the RNTI is equal to atleast one additional G-RNTI of the plurality of G-RNTIs.

In a nineteenth aspect, alone or in combination with the seventeenthaspect, at least one additional payload is scrambled according to thePDCCH payload scrambling sequence based on at least one additional valueof the RNTI, wherein the at least one additional value of the RNTI isequal to the value of the RNTI.

In a twentieth aspect, alone or in combination with the nineteenthaspect, the value of the RNTI is equal to a specified G-RNTI of theplurality of G-RNTIs.

In a twenty-first aspect, alone or in combination with one or more ofthe nineteenth through twentieth aspects, the plurality of G-RNTIs areconfigured using a G-RNTI list, and wherein the value of the RNTI isequal to a first listed G-RNTI of the G-RNTI list.

In a twenty-second aspect, alone or in combination with one or more ofthe nineteenth through twenty-first aspects, the value of the RNTI isequal to a G-RNTI mapped to a multicast service.

In a twenty-third aspect, alone or in combination with the twenty-secondaspect, the multicast service comprises a specified multicast service IDof a plurality of multicast service IDs.

In a twenty-fourth aspect, alone or in combination with the nineteenthaspect, the value of the RNTI comprises a configurable dedicated value.

In a twenty-fifth aspect, alone or in combination with one or more ofthe seventeenth through twenty-fourth aspects, the at least one MBSPDCCH communication comprises a plurality of MBS PDCCH communications.

In a twenty-sixth aspect, alone or in combination with one or more ofthe nineteenth through twenty-fifth aspects, process 500 includesmonitoring at least one additional search space for at least oneadditional MBS PDCCH that schedules at least one additional MBS PDSCHcommunication associated with at least one additional G-RNTI of theplurality of G-RNTIs.

In a twenty-seventh aspect, alone or in combination with one or more ofthe first through twenty-sixth aspects, process 500 includes receivingan RRC configuration that indicates a mapping between the search spaceand the G-RNTI.

In a twenty-eighth aspect, alone or in combination with one or more ofthe first through third aspects, the at least one MBS PDCCHcommunication comprises a CRC scrambled using a G-RNTI.

In a twenty-ninth aspect, alone or in combination with the twenty-eighthaspect, the at least one MBS PDCCH communication schedules a pluralityof MBS PDSCH communications, wherein each MBS PDSCH communication of theplurality of MBS PDSCH communications is associated with a respectivegroup RNTI (G-RNTI) of a plurality of G-RNTIs that includes the G-RNTI.

In a thirtieth aspect, alone or in combination with the twenty-ninthaspect, wherein at least one additional payload is scrambled accordingto the PDCCH payload scrambling sequence based on at least oneadditional value of the G-RNTI, wherein the at least one additionalvalue of the RNTI is equal to at least one additional G-RNTI of theplurality of G-RNTIs.

In a thirty-first aspect, alone or in combination with one or more ofthe twenty-ninth or thirtieth aspects, at least one additional payloadis scrambled according to the PDCCH payload scrambling sequence based onat least one additional value of the RNTI, wherein the at least oneadditional value of the G-RNTI is equal to the value of the G-RNTI.

In a thirty-second aspect, alone or in combination with one or more ofthe twenty-ninth through thirty-first aspects, the value of the G-RNTIis equal to a specified G-RNTI of the plurality of G-RNTIs.

In a thirty-third aspect, alone or in combination with one or more ofthe twenty-ninth through thirty-second aspects, the plurality of G-RNTIsare configured using a G-RNTI list, and wherein the value of the G-RNTIis equal to a first listed G-RNTI of the G-RNTI list.

In a thirty-fourth aspect, alone or in combination with one or more ofthe twenty-ninth through thirty-third aspects, the value of the G-RNTIis equal to a G-RNTI mapped to a multicast service.

In a thirty-fifth aspect, alone or in combination with the thirty-fourthaspect, the multicast service comprises a specified multicast service IDof a plurality of multicast service IDs.

Although FIG. 5 shows example blocks of process 500, in some aspects,process 500 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 5 .Additionally, or alternatively, two or more of the blocks of process 500may be performed in parallel.

FIG. 6 is a diagram illustrating an example process 600 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 600 is an example where the UE (e.g., UE 404) performsoperations associated with PDCCH transmissions for MBS services.

As shown in FIG. 6 , in some aspects, process 600 may include monitoringa search space associated with a PDCCH corresponding to an MBS PDSCH forat least one MBS PDCCH communication having a CCE index corresponding toa hash function that is based on a value of an RNTI, wherein the valueof the RNTI is equal to a G-RNTI or zero (block 610). For example, theUE (e.g., using communication manager 140 and/or reception component1102, depicted in FIG. 11 ) may monitor a search space for at least oneMBS PDCCH communication having a CCE index corresponding to a hashfunction that is based on a value of an RNTI, wherein the value of theRNTI is equal to a G-RNTI or zero, as described above.

As further shown in FIG. 6 , in some aspects, process 600 may includereceiving the at least one MBS PDCCH communication (block 620). Forexample, the UE (e.g., using communication manager 140 and/or receptioncomponent 1102, depicted in FIG. 11 ) may receive the at least one MBSPDCCH communication, as described above.

Process 600 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, the value of the RNTI is equal to zero.

In a second aspect, the value of the RNTI is equal to the G-RNTI.

In a third aspect, process 600 includes receiving an indication of anRRC parameter that enables the RNTI to equal the G-RNTI, wherein thevalue of the RNTI is equal to the G-RNTI based on receiving theindication of the RRC parameter.

In a fourth aspect, the value of the RNTI is equal to zero based on adetermination that the UE has not received an indication of a radioresource control parameter that enables the RNTI to equal the G-RNTI.

In a fifth aspect, process 600 includes receiving a dedicatedconfiguration indication that configures the search space, wherein thevalue of the RNTI is equal to the G-RNTI based on receiving thededicated configuration indication.

In a sixth aspect, alone or in combination with the fifth aspect,receiving the dedicated configuration indication comprises receiving adedicated RRC message.

In a seventh aspect, alone or in combination with one or more of thefifth through sixth aspects, receiving the dedicated configurationindication comprises receiving an RRC message that indicates a dedicatedparameter.

In an eighth aspect, the value of the RNTI is equal to zero based on adetermination that the UE has not received a dedicated configurationindication that configures the search space.

In a ninth aspect, monitoring the search space comprises monitoring thesearch space only in an RRC connected state, and wherein the value ofthe RNTI is equal to the G-RNTI based on monitoring the search spaceonly in the RRC connected state.

In a tenth aspect, the value of the RNTI is equal to zero based on adetermination that the search space is not monitored only in an RRCconnected state.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the at least one MBS PDCCH communicationcomprises a DCI transmission that schedules an MBS PDSCH.

In a twelfth aspect, alone or in combination with the eleventh aspect,the value of the RNTI is equal to zero based on a determination that aDCI format of the DCI transmission is a DCI format 1_0.

In a thirteenth aspect, alone or in combination with the eleventhaspect, the value of the RNTI is equal to the G-RNTI based on adetermination that a DCI format of the DCI transmission is not a DCIformat 1_0.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, the at least one MBS PDCCHcommunication schedules a plurality of MBS PDSCH communications, whereineach MBS PDSCH communication of the plurality of MBS PDSCHcommunications is associated with a respective G-RNTI of a plurality ofG-RNTIs that includes the G-RNTI.

In a fifteenth aspect, alone or in combination with the fourteenthaspect, the value of the RNTI is equal to the G-RNTI and wherein atleast one additional CCE index corresponds to at least one additionalhash function that is based on at least one additional value of theRNTI, wherein the at least one additional value of the RNTI is equal toat least one additional G-RNTI of the plurality of G-RNTIs.

In a sixteenth aspect, alone or in combination with the fourteenthaspect, at least one additional hash function is based on at least oneadditional value of the RNTI, wherein the at least one additional valueof the RNTI is equal to the value of the RNTI.

In a seventeenth aspect, alone or in combination with the sixteenthaspect, the value of the RNTI is equal to a specified G-RNTI of theplurality of G-RNTIs.

In an eighteenth aspect, alone or in combination with one or more of thesixteenth through seventeenth aspects, the plurality of G-RNTIs areconfigured using a G-RNTI list, and wherein the value of the RNTI isequal to a first listed G-RNTI of the G-RNTI list.

In a nineteenth aspect, alone or in combination with one or more of thesixteenth through eighteenth aspects, the value of the RNTI is equal toa G-RNTI mapped to a multicast service.

In a twentieth aspect, alone or in combination with the nineteenthaspect, the multicast service comprises a specified multicast service IDof a plurality of multicast service IDs.

In a twenty-first aspect, alone or in combination with the sixteenthaspect, the value of the RNTI comprises a configurable dedicated value.

In a twenty-second aspect, alone or in combination with one or more ofthe fourteenth through twenty-first aspects, the at least one MBS PDCCHcommunication comprises a plurality of MBS PDCCH communications.

In a twenty-third aspect, alone or in combination with one or more ofthe fourteenth through twenty-second aspects, process 600 includesmonitoring at least one additional search space for at least oneadditional MBS PDCCH that schedules at least one additional MBS PDSCHcommunication associated with at least one additional G-RNTI of theplurality of G-RNTIs.

In a twenty-fourth aspect, alone or in combination with one or more ofthe first through twenty-third aspects, process 600 includes receivingan RRC configuration that indicates a mapping between the search spaceand the G-RNTI.

Although FIG. 6 shows example blocks of process 600, in some aspects,process 600 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 6 .Additionally, or alternatively, two or more of the blocks of process 600may be performed in parallel.

FIG. 7 is a diagram illustrating an example process 700 performed, forexample, by a UE, in accordance with the present disclosure. Exampleprocess 700 is an example where the UE (e.g., UE 404) performsoperations associated with PDCCH transmissions for MBS services.

As shown in FIG. 7 , in some aspects, process 700 may include receivingan MBS configuration that configures a plurality of G-RNTIs for a cell(block 710). For example, the UE (e.g., using communication manager 140and/or reception component 1102, depicted in FIG. 11 ) may receive anMBS configuration that configures a plurality of G-RNTIs for a cell, asdescribed above.

As further shown in FIG. 7 , in some aspects, process 700 may includemonitoring, based on the MBS configuration, at least one search spaceassociated with a PDCCH corresponding to an MBS PDSCH of the cell for atleast one MBS PDCCH communication that schedules at least one MBS PDSCHcommunication of a plurality of MBS PDSCH communications (block 720).For example, the UE (e.g., using communication manager 140 and/orreception component 1102, depicted in FIG. 11 ) may monitor, based onthe MBS configuration, at least one search space associated with a PDCCHcorresponding to an MBS PDSCH of the cell for at least one MBS PDCCHcommunication that schedules at least one MBS PDSCH communication of aplurality of MBS PDSCH communications, as described above.

Process 700 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, each MBS PDSCH communication of the plurality of MBSPDSCH communications is associated with a respective G-RNTI of theplurality of G-RNTIs.

In a second aspect, alone or in combination with the first aspect, atleast one G-RNTI of the plurality of G-RNTIs comprises a value of anRNTI associated with at least one of a PDCCH payload scramblingsequence, a hash function corresponding to a CCE index, or a CRCscrambling sequence.

In a third aspect, alone or in combination with the second aspect, thevalue of the RNTI is equal to the at least one G-RNTI and wherein atleast one additional value of the RNTI is equal to at least oneadditional G-RNTI of the plurality of G-RNTIs.

In a fourth aspect, alone or in combination with the second aspect, atleast one additional value of the RNTI is equal to the value of theRNTI.

In a fifth aspect, alone or in combination with the fourth aspect, thevalue of the RNTI is equal to a specified G-RNTI of the plurality ofG-RNTIs.

In a sixth aspect, alone or in combination with one or more of thefourth through fifth aspects, the plurality of G-RNTIs are configuredusing a G-RNTI list, and wherein the value of the RNTI is equal to afirst listed G-RNTI of the G-RNTI list.

In a seventh aspect, alone or in combination with one or more of thethird through sixth aspects, the at least one of the plurality ofG-RNTIs is mapped to a multicast service.

In an eighth aspect, alone or in combination with the seventh aspect,the multicast service comprises a specified multicast service ID of aplurality of multicast service IDs.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, process 700 includes receiving a configurationthat indicates a configurable dedicated value of an RNTI, wherein theconfigurable dedicated value of the RNTI is associated with at least oneof a PDCCH payload scrambling sequence, a hash function corresponding toa CCE index, or a CRC scrambling sequence.

In a tenth aspect, monitoring the at least one search space comprisesmonitoring one search space.

In an eleventh aspect, monitoring the at least one search spacecomprises monitoring a plurality of search spaces.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, process 700 includes receiving an RRCconfiguration that indicates a mapping between the at least one searchspace and at least one G-RNTI of the plurality of G-RNTIs.

Although FIG. 7 shows example blocks of process 700, in some aspects,process 700 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 7 .Additionally, or alternatively, two or more of the blocks of process 700may be performed in parallel.

FIG. 8 is a diagram illustrating an example process 800 performed, forexample, by a base station, in accordance with the present disclosure.Example process 800 is an example where the base station (e.g., networknode 402) performs operations associated with PDCCH transmissions forMBS services.

As shown in FIG. 8 , in some aspects, process 800 may includetransmitting an MBS configuration that indicates a PDCCH payloadscrambling sequence based on a value of an RNTI for a search spaceassociated with a PDCCH corresponding to an MBS PDSCH, wherein the valueof the RNTI is equal to a G-RNTI or zero (block 810). For example, thebase station (e.g., using communication manager 150 and/or transmissioncomponent 1204, depicted in FIG. 12 ) may transmit an MBS configurationthat indicates a PDCCH payload scrambling sequence based on a value ofan RNTI for a search space associated with a PDCCH corresponding to anMBS PDSCH, wherein the value of the RNTI is equal to a G-RNTI or zero,as described above.

As further shown in FIG. 8 , in some aspects, process 800 may includetransmitting at least one MBS PDCCH communication based at least in parton the configuration (block 820). For example, the base station (e.g.,using communication manager 150 and/or transmission component 1204,depicted in FIG. 12 ) may transmit at least one MBS PDCCH communicationbased at least in part on the configuration, as described above.

Process 800 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, the value of the RNTI is equal to zero, the methodfurther comprising transmitting a configuration of a PDCCH DMRSscrambling ID for a CORESET associated with the search space.

In a second aspect, the value of the RNTI is equal to zero, and whereinthe base station does not transmit a configuration of a PDCCH DMRSscrambling ID for a CORESET associated with the search space.

In a third aspect, the value of the RNTI is equal to zero, and a PDCCHDMRS scrambling ID is not supported for a control resource setassociated with the search space.

In a fourth aspect, the value of the RNTI is equal to the G-RNTI, themethod further comprising transmitting a configuration of a PDCCH DMRSscrambling ID for a CORESET associated with the search space.

In a fifth aspect, the value of the RNTI is equal to the G-RNTI, andwherein the base station does not transmit a configuration of a PDCCHDMRS scrambling ID for a CORESET associated with the search space.

In a sixth aspect, process 800 includes transmitting a configuration ofa PDCCH DMRS scrambling ID for a CORESET associated with the searchspace, wherein the value of the RNTI is equal to the G-RNTI based ontransmitting the configuration of the PDCCH DMRS scrambling ID.

In a seventh aspect, the base station does not transmit a configurationof a PDCCH DMRS scrambling ID for a CORESET associated with the searchspace, and wherein the value of the RNTI is equal to zero based on thebase station not transmitting the configuration of the PDCCH DMRSscrambling ID.

In an eighth aspect, process 800 includes transmitting a configurationof a PDCCH DMRS scrambling ID for a CORESET associated with the searchspace and transmitting a dedicated configuration indication thatconfigures the search space, wherein the value of the RNTI is equal tothe G-RNTI based on transmitting the configuration of the PDCCH DMRSscrambling ID and the dedicated configuration indication.

In a ninth aspect, alone or in combination with the eighth aspect,transmitting the dedicated configuration indication comprisestransmitting a dedicated RRC message.

In a tenth aspect, alone or in combination with one or more of theeighth through ninth aspects, transmitting the dedicated configurationindication comprises transmitting an RRC message that indicates adedicated parameter.

In an eleventh aspect, the value of the RNTI is equal to zero based on adetermination that the base station has not transmitted a configurationof a PDCCH DMRS scrambling ID for a CORESET associated with the searchspace and a dedicated configuration indication that configures thesearch space.

In a twelfth aspect, 800 includes transmitting, to a UE, a configurationof a PDCCH DMRS scrambling ID for a CORESET associated with the searchspace and transmitting a monitoring configuration that indicates thatthe UE is to monitor the search space only in an RRC connected state,wherein the value of the RNTI is equal to the G-RNTI based ontransmitting the configuration of the PDCCH DMRS scrambling ID and themonitoring configuration.

In a thirteenth aspect, the value of the RNTI is equal to zero based ona determination that the base station has not transmitted aconfiguration of a PDCCH DMRS scrambling ID for a CORESET associatedwith the search space and a determination that the search space is notmonitored only in an RRC connected state.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, the at least one MBS PDCCHcommunication comprises a DCI transmission that schedules an MBSphysical downlink shared channel.

In a fifteenth aspect, alone or in combination with the fourteenthaspect, the value of the RNTI is equal to zero based on a determinationthat a DCI format of the DCI transmission is a DCI format 1_0.

In a sixteenth aspect, alone or in combination with the fourteenthaspect, the value of the RNTI is equal to the G-RNTI based on adetermination that a DCI format of the DCI transmission is not a DCIformat 1_0.

In a seventeenth aspect, alone or in combination with one or more of thefirst through sixteenth aspects, the at least one MBS PDCCHcommunication schedules a plurality of MBS PDSCH communications, whereineach MBS PDSCH communication of the plurality of MBS PDSCHcommunications is associated with a respective G-RNTI of a plurality ofG-RNTIs that includes the G-RNTI.

In an eighteenth aspect, alone or in combination with the seventeenthaspects the value of the RNTI is equal to the G-RNTI and wherein atleast one additional payload is scrambled according to the PDCCH payloadscrambling sequence based on at least one additional value of the RNTI,wherein the at least one additional value of the RNTI is equal to atleast one additional G-RNTI of the plurality of G-RNTIs.

In a nineteenth aspect, alone or in combination with the seventeenthaspect, at least one additional payload is scrambled according to thePDCCH payload scrambling sequence based on at least one additional valueof the RNTI, wherein the at least one additional value of the RNTI isequal to the value of the RNTI.

In a twentieth aspect, alone or in combination with the nineteenthaspect, the value of the RNTI is equal to a specified G-RNTI of theplurality of G-RNTIs.

In a twenty-first aspect, alone or in combination with one or more ofthe nineteenth through twentieth aspects, the plurality of G-RNTIs areconfigured using a G-RNTI list, and wherein the value of the RNTI isequal to a first listed G-RNTI of the G-RNTI list.

In a twenty-second aspect, alone or in combination with one or more ofthe nineteenth through twenty-first aspects, the value of the RNTI isequal to a G-RNTI mapped to a multicast service.

In a twenty-third aspect, alone or in combination with the twenty-secondaspect, the multicast service comprises a specified multicast service IDof a plurality of multicast service IDs.

In a twenty-fourth aspect, alone or in combination with the nineteenthaspect, the value of the RNTI comprises a configurable dedicated value.

In a twenty-fifth aspect, alone or in combination with one or more ofthe seventeenth through twenty-fourth aspects, the at least one MBSPDCCH communication comprises a plurality of MBS PDCCH communications.

In a twenty-sixth aspect, alone or in combination with one or more ofthe seventeenth through twenty-fifth aspects, process 800 includestransmitting a monitoring configuration that indicates that a UE is tomonitor at least one additional search space for at least one additionalMBS PDCCH that schedules at least one additional MBS PDSCH communicationassociated with at least one additional G-RNTI of the plurality ofG-RNTIs.

In a twenty-seventh aspect, alone or in combination with one or more ofthe first through twenty-sixth aspects, process 800 includestransmitting an RRC configuration that indicates a mapping between thesearch space and the G-RNTI.

In a twenty-eighth aspect, alone or in combination with one or more ofthe first through third aspects, the at least one MBS PDCCHcommunication comprises a CRC scrambled using a G-RNTI.

In a twenty-ninth aspect, alone or in combination with the twenty-eighthaspect, the at least one MBS PDCCH communication schedules a pluralityof MBS PDSCH communications, wherein each MBS PDSCH communication of theplurality of MBS PDSCH communications is associated with a respectivegroup RNTI (G-RNTI) of a plurality of G-RNTIs that includes the G-RNTI.

In a thirtieth aspect, alone or in combination with the twenty-ninthaspect, wherein at least one additional payload is scrambled accordingto the PDCCH payload scrambling sequence based on at least oneadditional value of the G-RNTI, wherein the at least one additionalvalue of the G-RNTI is equal to at least one additional G-RNTI of theplurality of G-RNTIs.

In a thirty-first aspect, alone or in combination with one or more ofthe twenty-ninth or thirtieth aspects, at least one additional payloadis scrambled according to the PDCCH payload scrambling sequence based onat least one additional value of the RNTI, wherein the at least oneadditional value of the G-RNTI is equal to the value of the G-RNTI.

In a thirty-second aspect, alone or in combination with one or more ofthe twenty-ninth through thirty-first aspects, the value of the G-RNTIis equal to a specified G-RNTI of the plurality of G-RNTIs.

In a thirty-third aspect, alone or in combination with one or more ofthe twenty-ninth through thirty-second aspects, the plurality of G-RNTIsare configured using a G-RNTI list, and wherein the value of the G-RNTIis equal to a first listed G-RNTI of the G-RNTI list.

In a thirty-fourth aspect, alone or in combination with one or more ofthe twenty-ninth through thirty-third aspects, the value of the G-RNTIis equal to a G-RNTI mapped to a multicast service.

In a thirty-fifth aspect, alone or in combination with the thirty-fourthaspect, the multicast service comprises a specified multicast service IDof a plurality of multicast service IDs.

Although FIG. 8 shows example blocks of process 800, in some aspects,process 800 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 8 .Additionally, or alternatively, two or more of the blocks of process 800may be performed in parallel.

FIG. 9 is a diagram illustrating an example process 900 performed, forexample, by a base station, in accordance with the present disclosure.Example process 900 is an example where the base station (e.g., networknode 402) performs operations associated with PDCCH transmissions forMBS services.

As shown in FIG. 9 , in some aspects, process 900 may includetransmitting an MB S configuration that indicates a PDCCH hash functionbased on a value of an RNTI for a search space associated with a PDCCHcorresponding to an MBS PDSCH, wherein the value of the RNTI is equal toa G-RNTI or zero (block 910). For example, the base station (e.g., usingcommunication manager 150 and/or transmission component 1204, depictedin FIG. 12 ) may transmit an MBS configuration that indicates a PDCCHhash function based on a value of an RNTI for a search space associatedwith a PDCCH corresponding to an MBS PDSCH, wherein the value of theRNTI is equal to a G-RNTI or zero, as described above.

As further shown in FIG. 9 , in some aspects, process 900 may includetransmitting at least one MBS PDCCH communication based at least in parton the configuration (block 920). For example, the base station (e.g.,using communication manager 150 and/or transmission component 1204,depicted in FIG. 12 ) may transmit at least one MBS PDCCH communicationbased at least in part on the configuration, as described above.

Process 900 may include additional aspects, such as any single aspect orany combination of aspects described below and/or in connection with oneor more other processes described elsewhere herein.

In a first aspect, the value of the RNTI is equal to zero.

In a second aspect, the value of the RNTI is equal to the G-RNTI.

In a third aspect, process 900 includes transmitting an indication of anRRC parameter that enables the RNTI to equal the G-RNTI, wherein thevalue of the RNTI is equal to the G-RNTI based on transmitting theindication of the RRC parameter.

In a fourth aspect, the value of the RNTI is equal to zero based on adetermination that the base station has not transmitted an indication ofan RRC parameter that enables the RNTI to equal the G-RNTI.

In a fifth aspect, process 900 includes transmitting a dedicatedconfiguration indication that configures the search space, wherein thevalue of the RNTI is equal to the G-RNTI based on transmitting thededicated configuration indication.

In a sixth aspect, alone or in combination with the fifth aspect,transmitting the dedicated configuration indication comprisestransmitting a dedicated RRC message.

In a seventh aspect, alone or in combination with one or more of thefifth through sixth aspects, transmitting the dedicated configurationindication comprises transmitting an RRC message that indicates adedicated parameter.

In an eighth aspect, the value of the RNTI is equal to zero based on adetermination that the base station has not transmitted a dedicatedconfiguration indication that configures the search space.

In a ninth aspect, transmitting a monitoring configuration thatindicates that a UE is to monitor the search space only in an RRCconnected state, and wherein the value of the RNTI is equal to theG-RNTI based on the monitoring configuration.

In a tenth aspect, the value of the RNTI is equal to zero based on adetermination that the search space is not monitored only in an RRCconnected state.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, the at least one MBS PDCCH communicationcomprises a DCI transmission that schedules an MBS PDSCH.

In a twelfth aspect, alone or in combination with the eleventh aspect,the value of the RNTI is equal to zero based on a determination that aDCI format of the DCI transmission is a DCI format 1_0.

In a thirteenth aspect, alone or in combination with the eleventhaspect, the value of the RNTI is equal to the G-RNTI based on adetermination that a DCI format of the DCI transmission is not a DCIformat 1_0.

In a fourteenth aspect, alone or in combination with one or more of thefirst through thirteenth aspects, the at least one MBS PDCCHcommunication schedules a plurality of MBS PDSCH communications, whereineach MBS PDSCH communication of the plurality of MBS PDSCHcommunications is associated with a respective G-RNTI of a plurality ofG-RNTIs that includes the G-RNTI.

In a fifteenth aspect, alone or in combination with the fourteenthaspect, the value of the RNTI is equal to the G-RNTI and wherein atleast one additional CCE index corresponds to at least one additionalhash function that is based on at least one additional value of theRNTI, wherein the at least one additional value of the RNTI is equal toat least one additional G-RNTI of the plurality of G-RNTIs.

In a sixteenth aspect, alone or in combination with the fourteenthaspect, at least one additional hash function is based on at least oneadditional value of the RNTI, wherein the at least one additional valueof the RNTI is equal to the value of the RNTI.

In a seventeenth aspect, alone or in combination with the sixteenthaspect, the value of the RNTI is equal to a specified G-RNTI of theplurality of G-RNTIs.

In an eighteenth aspect, alone or in combination with one or more of thesixteenth through seventeenth aspects, the plurality of G-RNTIs areconfigured using a G-RNTI list, and wherein the value of the RNTI isequal to a first listed G-RNTI of the G-RNTI list.

In a nineteenth aspect, alone or in combination with one or more of thesixteenth through eighteenth aspects, the value of the RNTI is equal toa G-RNTI mapped to a multicast service.

In a twentieth aspect, alone or in combination with the nineteenthaspect, the multicast service comprises a specified multicast service IDof a plurality of multicast service IDs.

In a twenty-first aspect, alone or in combination with the seventeenthaspect, the value of the RNTI comprises a configurable dedicated value.

In a twenty-second aspect, alone or in combination with one or more ofthe fifteenth through twenty-first aspects, the at least one MBS PDCCHcommunication comprises a plurality of MBS PDCCH communications.

In a twenty-third aspect, alone or in combination with one or more ofthe fifteenth through twenty-second aspects, process 900 includestransmitting a monitoring configuration that indicates that a UE is tomonitor at least one additional search space for at least one additionalMBS PDCCH that schedules at least one additional MBS PDSCH communicationassociated with at least one additional G-RNTI of the plurality ofG-RNTIs.

In a twenty-fourth aspect, alone or in combination with one or more ofthe first through twenty-third aspects, process 900 includestransmitting an RRC configuration that indicates a mapping between thesearch space and the G-RNTI.

Although FIG. 9 shows example blocks of process 900, in some aspects,process 900 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 9 .Additionally, or alternatively, two or more of the blocks of process 900may be performed in parallel.

FIG. 10 is a diagram illustrating an example process 1000 performed, forexample, by a base station, in accordance with the present disclosure.Example process 1000 is an example where the base station (e.g., networknode 402) performs operations associated with PDCCH transmissions forMBS services.

As shown in FIG. 10 , in some aspects, process 1000 may includetransmitting an MB S configuration that configures a plurality ofG-RNTIs for a cell (block 1010). For example, the base station (e.g.,using communication manager 150 and/or transmission component 1204,depicted in FIG. 12 ) may transmit an MBS configuration that configuresa plurality of G-RNTIs for a cell, as described above.

As further shown in FIG. 10 , in some aspects, process 1000 may includetransmitting, based on the MBS configuration and using at least onesearch space associated with a PDCCH corresponding to an MBS PDSCH ofthe cell, at least one MBS PDCCH communication that schedules at leastone MBS PDSCH communication of a plurality of MBS PDSCH communications(block 1020). For example, the base station (e.g., using communicationmanager 150 and/or transmission component 1204, depicted in FIG. 12 )may transmit, based on the MBS configuration and using at least onesearch space associated with a PDCCH corresponding to an MBS PDSCH ofthe cell, at least one MBS PDCCH communication that schedules at leastone MBS PDSCH communication of a plurality of MBS PDSCH communications,as described above.

Process 1000 may include additional aspects, such as any single aspector any combination of aspects described below and/or in connection withone or more other processes described elsewhere herein.

In a first aspect, each MBS PDSCH communication of the plurality of MBSPDSCH communications is associated with a respective G-RNTI of theplurality of G-RNTIs.

In a second aspect, alone or in combination with the first aspect, atleast one G-RNTI of the plurality of G-RNTIs comprises a value of anRNTI associated with at least one of a PDCCH payload scramblingsequence, a hash function corresponding to a CCE index, or a CRCscrambling sequence.

In a third aspect, the value of the RNTI is equal to the at least oneG-RNTI and wherein at least one additional value of the RNTI is equal toat least one additional G-RNTI of the plurality of G-RNTIs.

In a fourth aspect, at least one additional value of the RNTI is equalto the value of the RNTI.

In a fifth aspect, alone or in combination with the fourth aspect, thevalue of the RNTI is equal to a specified G-RNTI of the plurality ofG-RNTIs.

In a sixth aspect, alone or in combination with one or more of thefourth through fifth aspects, the plurality of G-RNTIs are configuredusing a G-RNTI list, and wherein the value of the RNTI is equal to afirst listed G-RNTI of the G-RNTI list.

In a seventh aspect, alone or in combination with one or more of thefirst through sixth aspects, the at least one of the plurality ofG-RNTIs is mapped to a multicast service.

In an eighth aspect, alone or in combination with the seventh aspect,the multicast service comprises a specified multicast service ID of aplurality of multicast service IDs.

In a ninth aspect, alone or in combination with one or more of the firstthrough eighth aspects, process 1000 includes transmitting aconfiguration that indicates a configurable dedicated value of an RNTI,wherein the configurable dedicated value of the RNTI is associated withat least one of a PDCCH payload scrambling sequence, a hash functioncorresponding to a CCE index, or a CRC scrambling sequence.

In a tenth aspect, alone or in combination with one or more of the firstthrough ninth aspects, process 1000 includes transmitting a monitoringconfiguration that indicates that a UE is to monitor the at least onesearch space comprises monitoring one search space.

In an eleventh aspect, alone or in combination with one or more of thefirst through tenth aspects, process 1000 includes transmitting amonitoring configuration that indicates that a UE is to monitor the atleast one search space comprises monitoring a plurality of searchspaces.

In a twelfth aspect, alone or in combination with one or more of thefirst through eleventh aspects, process 1000 includes transmitting anRRC configuration that indicates a mapping between the at least onesearch space and at least one G-RNTI of the plurality of G-RNTIs.

Although FIG. 10 shows example blocks of process 1000, in some aspects,process 1000 may include additional blocks, fewer blocks, differentblocks, or differently arranged blocks than those depicted in FIG. 10 .Additionally, or alternatively, two or more of the blocks of process1000 may be performed in parallel.

FIG. 11 is a diagram of an example apparatus 1100 for wirelesscommunication. The apparatus 1100 may be a UE, or a UE may include theapparatus 1100. In some aspects, the apparatus 1100 includes a receptioncomponent 1102 and a transmission component 1104, which may be incommunication with one another (for example, via one or more busesand/or one or more other components). As shown, the apparatus 1100 maycommunicate with another apparatus 1106 (such as a UE, a base station,or another wireless communication device) using the reception component1102 and the transmission component 1104. As further shown, theapparatus 1100 may include the communication manager 140.

In some aspects, the apparatus 1100 may be configured to perform one ormore operations described herein in connection with FIG. 4 .Additionally, or alternatively, the apparatus 1100 may be configured toperform one or more processes described herein, such as process 500 ofFIG. 5 , process 600 of FIG. 6 , process 700 of FIG. 7 , or acombination thereof. In some aspects, the apparatus 1100 and/or one ormore components shown in FIG. 11 may include one or more components ofthe UE described in connection with FIG. 2 . Additionally, oralternatively, one or more components shown in FIG. 11 may beimplemented within one or more components described in connection withFIG. 2 . Additionally, or alternatively, one or more components of theset of components may be implemented at least in part as software storedin a memory. For example, a component (or a portion of a component) maybe implemented as instructions or code stored in a non-transitorycomputer-readable medium and executable by a controller or a processorto perform the functions or operations of the component.

The reception component 1102 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 1106. The reception component1102 may provide received communications to one or more other componentsof the apparatus 1100. In some aspects, the reception component 1102 mayperform signal processing on the received communications (such asfiltering, amplification, demodulation, analog-to-digital conversion,demultiplexing, deinterleaving, de-mapping, equalization, interferencecancellation, or decoding, among other examples), and may provide theprocessed signals to the one or more other components of the apparatus1100. In some aspects, the reception component 1102 may include one ormore antennas, a modem, a demodulator, a MIMO detector, a receiveprocessor, a controller/processor, a memory, or a combination thereof,of the UE described in connection with FIG. 2 .

The transmission component 1104 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 1106. In some aspects, one or moreother components of the apparatus 1100 may generate communications andmay provide the generated communications to the transmission component1104 for transmission to the apparatus 1106. In some aspects, thetransmission component 1104 may perform signal processing on thegenerated communications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 1106. In some aspects, the transmission component 1104may include one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the UE described in connection with FIG. 2 . Insome aspects, the transmission component 1104 may be co-located with thereception component 1102 in a transceiver.

The communication manager 140 and/or reception component 1102 maymonitor a search space associated with a PDCCH corresponding to an MBSPDSCH for at least one MBS PDCCH communication having a payload that isscrambled according to a PDCCH payload scrambling sequence based on avalue of an RNTI, wherein the value of the RNTI is equal to a G-RNTI orzero. The reception component 1102 may receive the at least one MBSPDCCH communication. In some aspects, the communication manager 140 mayinclude one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the UE described in connection with FIG. 2 . Insome aspects, the communication manager 140 may include the receptioncomponent 1102 and/or the transmission component 1104.

The reception component 1102 may receive a configuration of a PDCCH DMRSscrambling ID for a control resource set associated with the searchspace, wherein the value of the RNTI is equal to the G-RNTI based onreceiving the configuration of the PDCCH DMRS scrambling ID. Thereception component 1102 may receive a configuration of a PDCCH DMRSscrambling ID for a CORESET associated with the search space.

The reception component 1102 may receive a dedicated configurationindication that configures the search space, wherein the value of theRNTI is equal to the G-RNTI based on receiving the configuration of thePDCCH DMRS scrambling ID and the dedicated configuration indication.

The reception component 1102 may receive a configuration of a PDCCH DMRSscrambling ID for a CORESET associated with the search space whereinmonitoring the search space comprises monitoring the search space onlyin an RRC connected state, and wherein the value of the RNTI is equal tothe G-RNTI based on receiving the configuration of the PDCCH DMRSscrambling ID and monitoring the search space only in the RRC connectedstate.

The communication manager 140 and/or reception component 1102 maymonitor at least one additional search space for at least one additionalMBS PDCCH that schedules at least one additional MBS PDSCH communicationassociated with at least one additional G-RNTI of the plurality ofG-RNTIs.

The reception component 1102 may receive an RRC configuration thatindicates a mapping between the search space and the G-RNTI.

The communication manager 140 and/or reception component 1102 maymonitor a search space associated with a PDCCH corresponding to an MBSPDSCH for at least one MBS PDCCH communication having a CCE indexcorresponding to a hash function that is based on a value of an RNTI,wherein the value of the RNTI is equal to a G-RNTI or zero. Thereception component 1102 may receive the at least one MB S PDCCHcommunication.

The reception component 1102 may receive an indication of an RRCparameter that enables the RNTI to equal the G-RNTI, wherein the valueof the RNTI is equal to the G-RNTI based on receiving the indication ofthe RRC parameter.

The reception component 1102 may receive a dedicated configurationindication that configures the search space, wherein the value of theRNTI is equal to the G-RNTI based on receiving the dedicatedconfiguration indication.

The communication manager 140 and/or reception component 1102 maymonitor at least one additional search space for at least one additionalMBS PDCCH that schedules at least one additional MBS PDSCH communicationassociated with at least one additional G-RNTI of the plurality ofG-RNTIs.

The reception component 1102 may receive an RRC configuration thatindicates a mapping between the search space and the G-RNTI.

The reception component 1102 may receive an MBS configuration thatconfigures a plurality of G-RNTIs for a cell. The communication manager140 and/or reception component 1102 may monitor, based on the MBSconfiguration, at least one search space associated with a PDCCHcorresponding to an MBS PDSCH of the cell for at least one MBS PDCCHcommunication that schedules at least one MBS PDSCH communication of aplurality of MBS PDSCH communications.

The reception component 1102 may receive a configuration that indicatesa configurable dedicated value of an RNTI, wherein the configurablededicated value of the RNTI is associated with at least one of a PDCCHpayload scrambling sequence, a hash function corresponding to a CCEindex, or a CRC scrambling sequence.

The reception component 1102 may receive a radio resource controlconfiguration that indicates a mapping between the at least one searchspace and at least one G-RNTI of the plurality of G-RNTIs.

The number and arrangement of components shown in FIG. 11 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 11 . Furthermore, two or more components shownin FIG. 11 may be implemented within a single component, or a singlecomponent shown in FIG. 11 may be implemented as multiple, distributedcomponents. Additionally, or alternatively, a set of (one or more)components shown in FIG. 11 may perform one or more functions describedas being performed by another set of components shown in FIG. 11 .

FIG. 12 is a diagram of an example apparatus 1200 for wirelesscommunication. The apparatus 1200 may be a base station, or a basestation may include the apparatus 1200. In some aspects, the apparatus1200 includes a reception component 1202 and a transmission component1204, which may be in communication with one another (for example, viaone or more buses and/or one or more other components). As shown, theapparatus 1200 may communicate with another apparatus 1206 (such as aUE, a base station, or another wireless communication device) using thereception component 1202 and the transmission component 1204. As furthershown, the apparatus 1200 may include the communication manager 150.

In some aspects, the apparatus 1200 may be configured to perform one ormore operations described herein in connection with FIG. 4 .Additionally, or alternatively, the apparatus 1200 may be configured toperform one or more processes described herein, such as process 800 ofFIG. 8 , process 900 of FIG. 9 , process 1000 of FIG. 10 , or acombination thereof. In some aspects, the apparatus 1200 and/or one ormore components shown in FIG. 12 may include one or more components ofthe base station described in connection with FIG. 2 . Additionally, oralternatively, one or more components shown in FIG. 12 may beimplemented within one or more components described in connection withFIG. 2 . Additionally, or alternatively, one or more components of theset of components may be implemented at least in part as software storedin a memory. For example, a component (or a portion of a component) maybe implemented as instructions or code stored in a non-transitorycomputer-readable medium and executable by a controller or a processorto perform the functions or operations of the component.

The reception component 1202 may receive communications, such asreference signals, control information, data communications, or acombination thereof, from the apparatus 1206. The reception component1202 may provide received communications to one or more other componentsof the apparatus 1200. In some aspects, the reception component 1202 mayperform signal processing on the received communications (such asfiltering, amplification, demodulation, analog-to-digital conversion,demultiplexing, deinterleaving, de-mapping, equalization, interferencecancellation, or decoding, among other examples), and may provide theprocessed signals to the one or more other components of the apparatus1200. In some aspects, the reception component 1202 may include one ormore antennas, a modem, a demodulator, a MIMO detector, a receiveprocessor, a controller/processor, a memory, or a combination thereof,of the base station described in connection with FIG. 2 .

The transmission component 1204 may transmit communications, such asreference signals, control information, data communications, or acombination thereof, to the apparatus 1206. In some aspects, one or moreother components of the apparatus 1200 may generate communications andmay provide the generated communications to the transmission component1204 for transmission to the apparatus 1206. In some aspects, thetransmission component 1204 may perform signal processing on thegenerated communications (such as filtering, amplification, modulation,digital-to-analog conversion, multiplexing, interleaving, mapping, orencoding, among other examples), and may transmit the processed signalsto the apparatus 1206. In some aspects, the transmission component 1204may include one or more antennas, a modem, a modulator, a transmit MIMOprocessor, a transmit processor, a controller/processor, a memory, or acombination thereof, of the base station described in connection withFIG. 2. In some aspects, the transmission component 1204 may beco-located with the reception component 1202 in a transceiver.

The communication manager 150 and/or transmission component 1204 maygenerate and transmit an MBS configuration that indicates a PDCCHpayload scrambling sequence based on a value of an RNTI for a searchspace associated with a PDCCH corresponding to an MBS PDSCH, wherein thevalue of the RNTI is equal to a G-RNTI or zero. The transmissioncomponent 1204 may transmit at least one MB S PDCCH communication basedat least in part on the configuration. In some aspects, thecommunication manager 150 may include one or more antennas, a modem, amodulator, a transmit MIMO processor, a transmit processor, acontroller/processor, a memory, or a combination thereof, of the basestation described in connection with FIG. 2 . In some aspects, thecommunication manager 150 may include the reception component 1202and/or the transmission component 1204.

The transmission component 1204 may transmit a configuration of a PDCCHDMRS scrambling ID for a control resource set associated with the searchspace, wherein the value of the RNTI is equal to the G-RNTI based ontransmitting the configuration of the PDCCH DMRS scrambling ID.

The transmission component 1204 may transmit a configuration of a PDCCHDMRS scrambling ID for a CORESET associated with the search space.

The transmission component 1204 may transmit a dedicated configurationindication that configures the search space, wherein the value of theRNTI is equal to the G-RNTI based on transmitting the configuration ofthe PDCCH DMRS scrambling ID and the dedicated configuration indication.

The transmission component 1204 may transmit, to a UE, a configurationof a PDCCH DMRS scrambling ID for a CORESET associated with the searchspace.

The transmission component 1204 may transmit a monitoring configurationthat indicates that the UE is to monitor the search space only in an RRCconnected state wherein the value of the RNTI is equal to the G-RNTIbased on transmitting the configuration of the PDCCH DMRS scrambling IDand the monitoring configuration.

The transmission component 1204 may transmit a monitoring configurationthat indicates that a UE is to monitor at least one additional searchspace for at least one additional MBS PDCCH that schedules at least oneadditional MBS PDSCH communication associated with at least oneadditional G-RNTI of the plurality of G-RNTIs.

The transmission component 1204 may transmit a radio resource controlconfiguration that indicates a mapping between the search space and theG-RNTI.

The transmission component 1204 may transmit an MBS configuration thatindicates a PDCCH hash function based on a value of an RNTI for a searchspace associated with a PDCCH corresponding to an MBS PDSCH, wherein thevalue of the RNTI is equal to a G-RNTI or zero. The transmissioncomponent 1204 may transmit at least one MBS PDCCH communication basedat least in part on the configuration.

The transmission component 1204 may transmit an indication of an RRCparameter that enables the RNTI to equal the G-RNTI, wherein the valueof the RNTI is equal to the G-RNTI based on transmitting the indicationof the RRC parameter.

The transmission component 1204 may transmit a dedicated configurationindication that configures the search space, wherein the value of theRNTI is equal to the G-RNTI based on transmitting the dedicatedconfiguration indication.

The transmission component 1204 may transmit a monitoring configurationthat indicates that a UE is to monitor at least one additional searchspace for at least one additional MBS PDCCH that schedules at least oneadditional MBS PDSCH communication associated with at least oneadditional G-RNTI of the plurality of G-RNTIs.

The transmission component 1204 may transmit a radio resource controlconfiguration that indicates a mapping between the search space and theG-RNTI.

The transmission component 1204 may transmit an MBS configuration thatconfigures a plurality of G-RNTIs for a cell. The transmission component1204 may transmit, based on the MBS configuration and using at least onesearch space associated with a PDCCH corresponding to an MBS PDSCH ofthe cell, at least one MBS PDCCH communication that schedules at leastone MBS PDSCH communication of a plurality of MBS PDSCH communications.

The transmission component 1204 may transmit a configuration thatindicates a configurable dedicated value of an RNTI, wherein theconfigurable dedicated value of the RNTI is associated with at least oneof a PDCCH payload scrambling sequence, a hash function corresponding toa CCE index, or a CRC scrambling sequence.

The transmission component 1204 may transmit a monitoring configurationthat indicates that a UE is to monitor the at least one search spacecomprises monitoring one search space.

The transmission component 1204 may transmit a monitoring configurationthat indicates that a UE is to monitor the at least one search spacecomprises monitoring a plurality of search spaces.

The transmission component 1204 may transmit a radio resource controlconfiguration that indicates a mapping between the at least one searchspace and at least one G-RNTI of the plurality of G-RNTIs.

The number and arrangement of components shown in FIG. 12 are providedas an example. In practice, there may be additional components, fewercomponents, different components, or differently arranged componentsthan those shown in FIG. 12 . Furthermore, two or more components shownin FIG. 12 may be implemented within a single component, or a singlecomponent shown in FIG. 12 may be implemented as multiple, distributedcomponents. Additionally, or alternatively, a set of (one or more)components shown in FIG. 12 may perform one or more functions describedas being performed by another set of components shown in FIG. 12 .

The following provides an overview of some Aspects of the presentdisclosure:

Aspect 1: A method of wireless communication performed by a userequipment (UE), comprising: monitoring a search space associated with aphysical downlink control channel (PDCCH) corresponding to amulticast/broadcast system (MBS) physical downlink shared channel(PDSCH) for at least one MBS PDCCH communication having a payload thatis scrambled according to a PDCCH payload scrambling sequence based on avalue of a radio network temporary identifier (RNTI), wherein the valueof the RNTI is equal to a group-RNTI (G-RNTI) or zero; and receiving theat least one MBS PDCCH communication.

Aspect 2: The method of Aspect 1, wherein the value of the RNTI is equalto zero, the method further comprising receiving a configuration of aPDCCH demodulation reference signal (DMRS) scrambling identifier for acontrol resource set associated with the search space.

Aspect 3: The method of Aspect 1, wherein the value of the RNTI is equalto zero, and wherein the UE does not receive a configuration of a PDCCHdemodulation reference signal (DMRS) scrambling identifier for a controlresource set associated with the search space.

Aspect 4: The method of Aspect 1, wherein the value of the RNTI is equalto zero, and a PDCCH demodulation reference signal (DMRS) scramblingidentifier is not supported for a control resource set associated withthe search space.

Aspect 5: The method of Aspect 1, wherein the value of the RNTI is equalto the G-RNTI, the method further comprising receiving a configurationof a PDCCH demodulation reference signal (DMRS) scrambling identifierfor a control resource set associated with the search space.

Aspect 6: The method of Aspect 1, wherein the value of the RNTI is equalto the G-RNTI, and wherein the UE does not receive a configuration of aPDCCH demodulation reference signal (DMRS) scrambling identifier for acontrol resource set associated with the search space.

Aspect 7: The method of Aspect 1, further comprising receiving aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier (ID) for a control resource set associated with the searchspace, wherein the value of the RNTI is equal to the G-RNTI based onreceiving the configuration of the PDCCH DMRS scrambling ID.

Aspect 8: The method of Aspect 1, wherein the UE does not receive aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier (ID) for a control resource set associated with the searchspace, and wherein the value of the RNTI is equal to zero based on theUE not receiving the configuration of the PDCCH DMRS scrambling ID.

Aspect 9: The method of Aspect 1, further comprising: receiving aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier (ID) for a control resource set associated with the searchspace; and receiving a dedicated configuration indication thatconfigures the search space, wherein the value of the RNTI is equal tothe G-RNTI based on receiving the configuration of the PDCCH DMRSscrambling ID and the dedicated configuration indication.

Aspect 10: The method of Aspect 9, wherein receiving the dedicatedconfiguration indication comprises receiving a dedicated radio resourcecontrol message.

Aspect 11: The method of either of Aspects 9 or 10, wherein receivingthe dedicated configuration indication comprises receiving a radioresource control message that indicates a dedicated parameter.

Aspect 12: The method of Aspect 1, wherein the value of the RNTI isequal to zero based on a determination that the UE has not received aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier (ID) for a control resource set associated with the searchspace and a dedicated configuration indication that configures thesearch space.

Aspect 13: The method of Aspect 1, further comprising: receiving aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier (ID) for a control resource set associated with the searchspace, wherein monitoring the search space comprises monitoring thesearch space only in a radio resource control (RRC) connected state, andwherein the value of the RNTI is equal to the G-RNTI based on receivingthe configuration of the PDCCH DMRS scrambling ID and monitoring thesearch space only in the RRC connected state.

Aspect 14: The method of Aspect 1, wherein the value of the RNTI isequal to zero based on a determination that the UE has not received aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier (ID) for a control resource set associated with the searchspace and a determination that the search space is not monitored only ina radio resource control connected state.

Aspect 15: The method of any of Aspects 1-14, wherein the at least oneMBS PDCCH communication comprises a downlink control information (DCI)transmission that schedules an MBS physical downlink shared channel.

Aspect 16: The method of Aspect 15, wherein the value of the RNTI isequal to zero based on a determination that a DCI format of the DCItransmission is a DCI format 1_0.

Aspect 17: The method of Aspect 15, wherein the value of the RNTI isequal to the G-RNTI based on a determination that a DCI format of theDCI transmission is not a DCI format 1_0.

Aspect 18: The method of any of Aspects 1-17, wherein the at least oneMBS PDCCH communication schedules a plurality of MBS physical downlinkshared channel (PDSCH) communications, wherein each MBS PDSCHcommunication of the plurality of MBS PDSCH communications is associatedwith a respective G-RNTI of a plurality of G-RNTIs that includes theG-RNTI.

Aspect 19: The method of Aspect 18, wherein the value of the RNTI isequal to the G-RNTI and wherein at least one additional payload isscrambled according to the PDCCH payload scrambling sequence based on atleast one additional value of the RNTI, wherein the at least oneadditional value of the RNTI is equal to at least one additional G-RNTIof the plurality of G-RNTIs.

Aspect 20: The method of Aspect 18, wherein at least one additionalpayload is scrambled according to the PDCCH payload scrambling sequencebased on at least one additional value of the RNTI, wherein the at leastone additional value of the RNTI is equal to the value of the RNTI.

Aspect 21: The method of Aspect 20, wherein the value of the RNTI isequal to a specified G-RNTI of the plurality of G-RNTIs.

Aspect 22: The method of either of Aspects 20 or 21, wherein theplurality of G-RNTIs are configured using a G-RNTI list, and wherein thevalue of the RNTI is equal to a first listed G-RNTI of the G-RNTI list.

Aspect 23: The method of any of Aspects 20-22, wherein the value of theRNTI is equal to a G-RNTI mapped to a multicast service.

Aspect 24: The method of Aspect 23, wherein the multicast servicecomprises a specified multicast service identifier (ID) of a pluralityof multicast service IDs.

Aspect 25: The method of Aspect 20, wherein the value of the RNTIcomprises a configurable dedicated value.

Aspect 26: The method of any of Aspects 18-25, wherein the at least oneMBS PDCCH communication comprises a plurality of MBS PDCCHcommunications.

Aspect 27: The method of any of Aspects 18-26, further comprisingmonitoring at least one additional search space for at least oneadditional MBS PDCCH that schedules at least one additional MBS PDSCHcommunication associated with at least one additional G-RNTI of theplurality of G-RNTIs.

Aspect 28: The method of any of Aspects 1-27, further comprisingreceiving a radio resource control configuration that indicates amapping between the search space and the G-RNTI.

Aspect 29: A method of wireless communication performed by a userequipment (UE), comprising: monitoring a search space associated with aphysical downlink control channel (PDCCH) corresponding to amulticast/broadcast system (MBS) physical downlink shared channel(PDSCH) for at least one MBS PDCCH communication having a controlchannel element (CCE) index corresponding to a hash function that isbased on a value of a radio network temporary identifier (RNTI), whereinthe value of the RNTI is equal to a group-RNTI (G-RNTI) or zero; andreceiving the at least one MBS PDCCH communication.

Aspect 30: The method of Aspect 29, wherein the value of the RNTI isequal to zero.

Aspect 31: The method of Aspect 29, wherein the value of the RNTI isequal to the G-RNTI.

Aspect 32: The method of Aspect 29, further comprising receiving anindication of a radio resource control (RRC) parameter that enables theRNTI to equal the G-RNTI, wherein the value of the RNTI is equal to theG-RNTI based on receiving the indication of the RRC parameter.

Aspect 33: The method of Aspect 29, wherein the value of the RNTI isequal to zero based on a determination that the UE has not received anindication of a radio resource control parameter that enables the RNTIto equal the G-RNTI.

Aspect 34: The method of Aspect 29, further comprising receiving adedicated configuration indication that configures the search space,wherein the value of the RNTI is equal to the G-RNTI based on receivingthe dedicated configuration indication.

Aspect 35: The method of Aspect 34, wherein receiving the dedicatedconfiguration indication comprises receiving a dedicated radio resourcecontrol message.

Aspect 36: The method of either of Aspect 34 or 35, wherein receivingthe dedicated configuration indication comprises receiving a radioresource control message that indicates a dedicated parameter.

Aspect 37: The method of Aspect 29, wherein the value of the RNTI isequal to zero based on a determination that the UE has not received adedicated configuration indication that configures the search space.

Aspect 38: The method of Aspect 29, wherein monitoring the search spacecomprises monitoring the search space only in a radio resource control(RRC) connected state, and wherein the value of the RNTI is equal to theG-RNTI based on monitoring the search space only in the RRC connectedstate.

Aspect 39: The method of Aspect 29, wherein the value of the RNTI isequal to zero based on a determination that the search space is notmonitored only in a radio resource control connected state.

Aspect 40: The method of any of Aspects 29-39, wherein the at least oneMBS PDCCH communication comprises a downlink control information (DCI)transmission that schedules an MBS physical downlink shared channel.

Aspect 41: The method of Aspect 40, wherein the value of the RNTI isequal to zero based on a determination that a DCI format of the DCItransmission is a DCI format 1_0.

Aspect 42: The method of Aspect 40, wherein the value of the RNTI isequal to the G-RNTI based on a determination that a DCI format of theDCI transmission is not a DCI format 1_0.

Aspect 43: The method of any of Aspects 29-42, wherein the at least oneMBS PDCCH communication schedules a plurality of MBS physical downlinkshared channel (PDSCH) communications, wherein each MBS PDSCHcommunication of the plurality of MBS PDSCH communications is associatedwith a respective G-RNTI of a plurality of G-RNTIs that includes theG-RNTI.

Aspect 44: The method of Aspect 43, wherein the value of the RNTI isequal to the G-RNTI and wherein at least one additional CCE indexcorresponds to at least one additional hash function that is based on atleast one additional value of the RNTI, wherein the at least oneadditional value of the RNTI is equal to at least one additional G-RNTIof the plurality of G-RNTIs.

Aspect 45: The method of Aspect 43, wherein at least one additional hashfunction is based on at least one additional value of the RNTI, whereinthe at least one additional value of the RNTI is equal to the value ofthe RNTI.

Aspect 46: The method of Aspect 45, wherein the value of the RNTI isequal to a specified G-RNTI of the plurality of G-RNTIs.

Aspect 47: The method of either of Aspects 45 or 46, wherein theplurality of G-RNTIs are configured using a G-RNTI list, and wherein thevalue of the RNTI is equal to a first listed G-RNTI of the G-RNTI list.

Aspect 48: The method of any of Aspects 45-47, wherein the value of theRNTI is equal to a G-RNTI mapped to a multicast service.

Aspect 49: The method of Aspect 48, wherein the multicast servicecomprises a specified multicast service identifier (ID) of a pluralityof multicast service IDs.

Aspect 50: The method of Aspect 45, wherein the value of the RNTIcomprises a configurable dedicated value.

Aspect 51: The method of any of Aspects 43-50, wherein the at least oneMBS PDCCH communication comprises a plurality of MBS PDCCHcommunications.

Aspect 52: The method of any of Aspects 43-51, further comprisingmonitoring at least one additional search space for at least oneadditional MBS PDCCH that schedules at least one additional MBS PDSCHcommunication associated with at least one additional G-RNTI of theplurality of G-RNTIs.

Aspect 53: The method of any of Aspects 29-52, further comprisingreceiving a radio resource control configuration that indicates amapping between the search space and the G-RNTI.

Aspect 54: A method of wireless communication performed by a userequipment (UE), comprising: receiving a multicast/broadcast system (MBS)configuration that configures a plurality of group radio networktemporary identifiers (G-RNTIs) for a cell; and monitoring, based on theMBS configuration, at least one search space associated with a physicaldownlink control channel (PDCCH) corresponding to an MBS physicaldownlink shared channel (PDSCH) of the cell for at least one MBS PDCCHcommunication that schedules at least one MBS PDSCH communication of aplurality of MBS PDSCH communications.

Aspect 55: The method of Aspect 54, wherein each MBS PDSCH communicationof the plurality of MBS PDSCH communications is associated with arespective G-RNTI of the plurality of G-RNTIs.

Aspect 56: The method of either of Aspects 54 or 55, wherein at leastone G-RNTI of the plurality of G-RNTIs comprises a value of an RNTIassociated with at least one of: a PDCCH payload scrambling sequence, ahash function corresponding to a control channel element index, or acyclic redundancy check scrambling sequence.

Aspect 57: The method of Aspect 56, wherein the value of the RNTI isequal to the at least one G-RNTI and wherein at least one additionalvalue of the RNTI is equal to at least one additional G-RNTI of theplurality of G-RNTIs.

Aspect 58: The method of Aspect 56, wherein at least one additionalvalue of the RNTI is equal to the value of the RNTI.

Aspect 59: The method of Aspect 58, wherein the value of the RNTI isequal to a specified G-RNTI of the plurality of G-RNTIs.

Aspect 60: The method of either of Aspects 58 or 59, wherein theplurality of G-RNTIs are configured using a G-RNTI list, and wherein thevalue of the RNTI is equal to a first listed G-RNTI of the G-RNTI list.

Aspect 61: The method of any of Aspects 56-60, wherein the at least oneof the plurality of G-RNTIs is mapped to a multicast service.

Aspect 62: The method of Aspect 61, wherein the multicast servicecomprises a specified multicast service identifier (ID) of a pluralityof multicast service IDs.

Aspect 63: The method of any of Aspects 54-62, further comprisingreceiving a configuration that indicates a configurable dedicated valueof an RNTI, wherein the configurable dedicated value of the RNTI isassociated with at least one of: a PDCCH payload scrambling sequence, ahash function corresponding to a control channel element index, or acyclic redundancy check scrambling sequence.

Aspect 64: The method of Aspect 54, wherein monitoring the at least onesearch space comprises monitoring one search space.

Aspect 65: The method of Aspect 54, wherein monitoring the at least onesearch space comprises monitoring a plurality of search spaces.

Aspect 66: The method of any of Aspects 54-65, further comprisingreceiving a radio resource control configuration that indicates amapping between the at least one search space and at least one G-RNTI ofthe plurality of G-RNTIs.

Aspect 67: A method of wireless communication performed by a basestation, comprising: transmitting a multicast/broadcast system (MBS)configuration that indicates a physical downlink control channel (PDCCH)payload scrambling sequence based on a value of a radio networktemporary identifier (RNTI) for a search space associated with aphysical downlink control channel (PDCCH) corresponding to an MBSphysical downlink shared channel (PDSCH), wherein the value of the RNTIis equal to a group-RNTI (G-RNTI) or zero; and transmitting at least oneMBS PDCCH communication based at least in part on the configuration.

Aspect 68: The method of Aspect 67, wherein the value of the RNTI isequal to zero, the method further comprising transmitting aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier for a control resource set associated with the search space.

Aspect 69: The method of Aspect 67, wherein the value of the RNTI isequal to zero, and wherein the base station does not transmit aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier for a control resource set associated with the search space.

Aspect 70: The method of Aspect 67, wherein the value of the RNTI isequal to zero, and a PDCCH demodulation reference signal (DMRS)scrambling identifier is not supported for a control resource setassociated with the search space.

Aspect 71: The method of Aspect 67, wherein the value of the RNTI isequal to the G-RNTI, the method further comprising transmitting aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier for a control resource set associated with the search space.

Aspect 72: The method of Aspect 67, wherein the value of the RNTI isequal to the G-RNTI, and wherein the base station does not transmit aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier for a control resource set associated with the search space.

Aspect 73: The method of Aspect 67, further comprising transmitting aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier (ID) for a control resource set associated with the searchspace, wherein the value of the RNTI is equal to the G-RNTI based ontransmitting the configuration of the PDCCH DMRS scrambling ID.

Aspect 74: The method of Aspect 67, wherein the base station does nottransmit a configuration of a PDCCH demodulation reference signal (DMRS)scrambling identifier (ID) for a control resource set associated withthe search space, and wherein the value of the RNTI is equal to zerobased on the base station not transmitting the configuration of thePDCCH DMRS scrambling ID.

Aspect 75: The method of Aspect 67, further comprising: transmitting aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier (ID) for a control resource set associated with the searchspace; and transmitting a dedicated configuration indication thatconfigures the search space, wherein the value of the RNTI is equal tothe G-RNTI based on transmitting the configuration of the PDCCH DMRSscrambling ID and the dedicated configuration indication.

Aspect 76: The method of Aspect 75, wherein transmitting the dedicatedconfiguration indication comprises transmitting a dedicated radioresource control message.

Aspect 77: The method of either of Aspects 75 or 76, whereintransmitting the dedicated configuration indication comprisestransmitting a radio resource control message that indicates a dedicatedparameter.

Aspect 78: The method of Aspect 67, wherein the value of the RNTI isequal to zero based on a determination that the base station has nottransmitted a configuration of a PDCCH demodulation reference signal(DMRS) scrambling identifier (ID) for a control resource set associatedwith the search space and a dedicated configuration indication thatconfigures the search space.

Aspect 79: The method of Aspect 67, further comprising: transmitting, toa user equipment (UE), a configuration of a PDCCH demodulation referencesignal (DMRS) scrambling identifier (ID) for a control resource setassociated with the search space; and transmitting a monitoringconfiguration that indicates that the UE is to monitor the search spaceonly in a radio resource control (RRC) connected state, wherein thevalue of the RNTI is equal to the G-RNTI based on transmitting theconfiguration of the PDCCH DMRS scrambling ID and the monitoringconfiguration.

Aspect 80: The method of Aspect 67, wherein the value of the RNTI isequal to zero based on a determination that the base station has nottransmitted a configuration of a PDCCH demodulation reference signal(DMRS) scrambling identifier (ID) for a control resource set associatedwith the search space and a determination that the search space is notmonitored only in a radio resource control connected state.

Aspect 81: The method of any of Aspects 67-80, wherein the at least oneMBS PDCCH communication comprises a downlink control information (DCI)transmission that schedules an MBS physical downlink shared channel.

Aspect 82: The method of Aspect 81, wherein the value of the RNTI isequal to zero based on a determination that a DCI format of the DCItransmission is a DCI format 1_0.

Aspect 83: The method of Aspect 81, wherein the value of the RNTI isequal to the G-RNTI based on a determination that a DCI format of theDCI transmission is not a DCI format 1_0.

Aspect 84: The method of any of Aspects 67-83, wherein the at least oneMBS PDCCH communication schedules a plurality of MBS physical downlinkshared channel (PDSCH) communications, wherein each MBS PDSCHcommunication of the plurality of MBS PDSCH communications is associatedwith a respective G-RNTI of a plurality of G-RNTIs that includes theG-RNTI.

Aspect 85: The method of Aspect 84, wherein the value of the RNTI isequal to the G-RNTI and wherein at least one additional payload isscrambled according to the PDCCH payload scrambling sequence based on atleast one additional value of the RNTI, wherein the at least oneadditional value of the RNTI is equal to at least one additional G-RNTIof the plurality of G-RNTIs.

Aspect 86: The method of Aspect 84, wherein at least one additionalpayload is scrambled according to the PDCCH payload scrambling sequencebased on at least one additional value of the RNTI, wherein the at leastone additional value of the RNTI is equal to the value of the RNTI.

Aspect 87: The method of Aspect 86, wherein the value of the RNTI isequal to a specified G-RNTI of the plurality of G-RNTIs.

Aspect 88: The method of either of Aspects 86 or 87, wherein theplurality of G-RNTIs are configured using a G-RNTI list, and wherein thevalue of the RNTI is equal to a first listed G-RNTI of the G-RNTI list.

Aspect 89: The method of any of Aspects 86-88, wherein the value of theRNTI is equal to a G-RNTI mapped to a multicast service.

Aspect 90: The method of Aspect 89, wherein the multicast servicecomprises a specified multicast service identifier (ID) of a pluralityof multicast service IDs.

Aspect 91: The method of Aspect 86, wherein the value of the RNTIcomprises a configurable dedicated value.

Aspect 92: The method of any of Aspects 84-91, wherein the at least oneMBS PDCCH communication comprises a plurality of MBS PDCCHcommunications.

Aspect 93: The method of any of Aspects 84-92, further comprisingtransmitting a monitoring configuration that indicates that a userequipment (UE) is to monitor at least one additional search space for atleast one additional MBS PDCCH that schedules at least one additionalMBS PDSCH communication associated with at least one additional G-RNTIof the plurality of G-RNTIs.

Aspect 94: The method of any of Aspects 67-93, further comprisingtransmitting a radio resource control configuration that indicates amapping between the search space and the G-RNTI.

Aspect 95: A method of wireless communication performed by a basestation, comprising: transmitting a multicast/broadcast system (MBS)configuration that indicates a physical downlink control channel (PDCCH)hash function based on a value of a radio network temporary identifier(RNTI) for a search space associated with a PDCCH corresponding to anMBS physical downlink shared channel (PDSCH), wherein the value of theRNTI is equal to a group-RNTI (G-RNTI) or zero; and transmitting atleast one MBS PDCCH communication based at least in part on theconfiguration.

Aspect 96: The method of Aspect 95, wherein the value of the RNTI isequal to zero.

Aspect 97: The method of Aspect 95, wherein the value of the RNTI isequal to the G-RNTI.

Aspect 98: The method of Aspect 95, further comprising transmitting anindication of a radio resource control (RRC) parameter that enables theRNTI to equal the G-RNTI, wherein the value of the RNTI is equal to theG-RNTI based on transmitting the indication of the RRC parameter.

Aspect 99: The method of Aspect 95, wherein the value of the RNTI isequal to zero based on a determination that the base station has nottransmitted an indication of a radio resource control parameter thatenables the RNTI to equal the G-RNTI.

Aspect 100: The method of Aspect 95, further comprising transmitting adedicated configuration indication that configures the search space,wherein the value of the RNTI is equal to the G-RNTI based ontransmitting the dedicated configuration indication.

Aspect 101: The method of Aspect 100, wherein transmitting the dedicatedconfiguration indication comprises transmitting a dedicated radioresource control message.

Aspect 102: The method of either of Aspects 100 or 101, whereintransmitting the dedicated configuration indication comprisestransmitting a radio resource control message that indicates a dedicatedparameter.

Aspect 103: The method of Aspect 95, wherein the value of the RNTI isequal to zero based on a determination that the base station has nottransmitted a dedicated configuration indication that configures thesearch space.

Aspect 104: The method of Aspect 95, wherein transmitting a monitoringconfiguration that indicates that a user equipment (UE) is to monitorthe search space only in a radio resource control (RRC) connected state,and wherein the value of the RNTI is equal to the G-RNTI based on themonitoring configuration.

Aspect 105: The method of Aspect 95, wherein the value of the RNTI isequal to zero based on a determination that the search space is notmonitored only in a radio resource control connected state.

Aspect 106: The method of any of Aspects 95-105, wherein the at leastone MBS PDCCH communication comprises a downlink control information(DCI) transmission that schedules an MBS physical downlink sharedchannel.

Aspect 107: The method of Aspect 106, wherein the value of the RNTI isequal to zero based on a determination that a DCI format of the DCItransmission is a DCI format 1_0.

Aspect 108: The method of Aspect 106, wherein the value of the RNTI isequal to the G-RNTI based on a determination that a DCI format of theDCI transmission is not a DCI format 1_0.

Aspect 109: The method of any of Aspects 95-108, wherein the at leastone MBS PDCCH communication schedules a plurality of MBS physicaldownlink shared channel (PDSCH) communications, wherein each MBS PDSCHcommunication of the plurality of MBS PDSCH communications is associatedwith a respective G-RNTI of a plurality of G-RNTIs that includes theG-RNTI.

Aspect 110: The method of Aspect 109, wherein the value of the RNTI isequal to the G-RNTI and wherein at least one additional CCE indexcorresponds to at least one additional hash function that is based on atleast one additional value of the RNTI, wherein the at least oneadditional value of the RNTI is equal to at least one additional G-RNTIof the plurality of G-RNTIs.

Aspect 111: The method of Aspect 109, wherein at least one additionalhash function is based on at least one additional value of the RNTI,wherein the at least one additional value of the RNTI is equal to thevalue of the RNTI.

Aspect 112: The method of Aspect 111, wherein the value of the RNTI isequal to a specified G-RNTI of the plurality of G-RNTIs.

Aspect 113: The method of either of Aspects 111 or 112, wherein theplurality of G-RNTIs are configured using a G-RNTI list, and wherein thevalue of the RNTI is equal to a first listed G-RNTI of the G-RNTI list.

Aspect 114: The method of any of Aspects 111-113, wherein the value ofthe RNTI is equal to a G-RNTI mapped to a multicast service.

Aspect 115: The method of Aspect 114, wherein the multicast servicecomprises a specified multicast service identifier (ID) of a pluralityof multicast service IDs.

Aspect 116: The method of Aspect 111, wherein the value of the RNTIcomprises a configurable dedicated value.

Aspect 117: The method of any of Aspects 109-116, wherein the at leastone MBS PDCCH communication comprises a plurality of MBS PDCCHcommunications.

Aspect 118: The method of any of Aspects 109-117, further comprisingtransmitting a monitoring configuration that indicates that a userequipment (UE) is to monitor at least one additional search space for atleast one additional MBS PDCCH that schedules at least one additionalMBS PDSCH communication associated with at least one additional G-RNTIof the plurality of G-RNTIs.

Aspect 119: The method of any of Aspects 95-118, further comprisingtransmitting a radio resource control configuration that indicates amapping between the search space and the G-RNTI.

Aspect 120: A method of wireless communication performed by a basestation, comprising: transmitting a multicast/broadcast system (MBS)configuration that configures a plurality of group radio networktemporary identifiers (G-RNTIs) for a cell; and transmitting, based onthe MBS configuration and using at least one search space associatedwith a physical downlink control channel (PDCCH) corresponding to an MBSphysical downlink shared channel (PDSCH) of the cell, at least one MBSPDCCH communication that schedules at least one MBS PDSCH communicationof a plurality of MBS PDSCH communications.

Aspect 121: The method of Aspect 120, wherein each MBS PDSCHcommunication of the plurality of MBS PDSCH communications is associatedwith a respective G-RNTI of the plurality of G-RNTIs.

Aspect 122: The method of either of Aspects 120 or 121, wherein at leastone G-RNTI of the plurality of G-RNTIs comprises a value of an RNTIassociated with at least one of: a PDCCH payload scrambling sequence, ahash function corresponding to a control channel element index, or acyclic redundancy check scrambling sequence.

Aspect 123: The method of Aspect 122, wherein the value of the RNTI isequal to the at least one G-RNTI and wherein at least one additionalvalue of the RNTI is equal to at least one additional G-RNTI of theplurality of G-RNTIs.

Aspect 124: The method of Aspect 122, wherein at least one additionalvalue of the RNTI is equal to the value of the RNTI.

Aspect 125: The method of Aspect 124, wherein the value of the RNTI isequal to a specified G-RNTI of the plurality of G-RNTIs.

Aspect 126: The method of either of Aspects 124 or 125, wherein theplurality of G-RNTIs are configured using a G-RNTI list, and wherein thevalue of the RNTI is equal to a first listed G-RNTI of the G-RNTI list.

Aspect 127: The method of any of Aspects 122-126, wherein the at leastone of the plurality of G-RNTIs is mapped to a multicast service.

Aspect 128: The method of Aspect 127, wherein the multicast servicecomprises a specified multicast service identifier (ID) of a pluralityof multicast service IDs.

Aspect 129: The method of any of Aspects 120-128, further comprisingtransmitting a configuration that indicates a configurable dedicatedvalue of an RNTI, wherein the configurable dedicated value of the RNTIis associated with at least one of: a PDCCH payload scrambling sequence,a hash function corresponding to a control channel element index, or acyclic redundancy check scrambling sequence.

Aspect 130: The method of any of Aspects 120-129, further comprisingtransmitting a monitoring configuration that indicates that a userequipment (UE) is to monitor the at least one search space comprisesmonitoring one search space.

Aspect 131: The method of any of Aspects 120-130, further comprisingtransmitting a monitoring configuration that indicates that a userequipment (UE) is to monitor the at least one search space comprisesmonitoring a plurality of search spaces.

Aspect 132: The method of any of Aspects 120-131, further comprisingtransmitting a radio resource control configuration that indicates amapping between the at least one search space and at least one G-RNTI ofthe plurality of G-RNTIs.

Aspect 133: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects1-28.

Aspect 134: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 1-28.

Aspect 135: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 1-28.

Aspect 136: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 1-28.

Aspect 137: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 1-28.

Aspect 138: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects29-53.

Aspect 139: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 29-53.

Aspect 140: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 29-53.

Aspect 141: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 29-53.

Aspect 142: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 29-53.

Aspect 143: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects54-66.

Aspect 144: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 54-66.

Aspect 145: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 54-66.

Aspect 146: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 54-66.

Aspect 147: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 54-66.

Aspect 148: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects67-94.

Aspect 149: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 67-94.

Aspect 150: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 67-94.

Aspect 151: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 67-94.

Aspect 152: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 67-94

Aspect 153: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects95-119.

Aspect 154: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 95-119.

Aspect 155: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 95-119.

Aspect 156: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 95-119.

Aspect 157: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 95-119.

Aspect 158: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects120-132.

Aspect 159: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 120-132.

Aspect 160: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 120-132.

Aspect 161: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 120-132.

Aspect 162: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 120-132.

Aspect 163: A method of wireless communication performed by a userequipment (UE), comprising: monitoring a search space associated with aphysical downlink control channel (PDCCH) corresponding to amulticast/broadcast system (MBS) physical downlink shared channel(PDSCH) for at least one MBS PDCCH communication having a payload thatis scrambled according to a PDCCH payload scrambling sequence based on avalue of a radio network temporary identifier (RNTI), wherein the valueof the RNTI is equal to zero; and receiving the at least one MB S PDCCHcommunication.

Aspect 164: The method of Aspect 163, the method further comprisingreceiving a configuration of a PDCCH demodulation reference signal(DMRS) scrambling identifier for a control resource set associated withthe search space.

Aspect 165: The method of Aspect 163, wherein the UE does not receive aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier for a control resource set associated with the search space.

Aspect 166: The method of Aspect 163, a PDCCH demodulation referencesignal (DMRS) scrambling identifier is not supported for a controlresource set associated with the search space.

Aspect 167: The method of Aspect 163, wherein the at least one MBS PDCCHcommunication comprises a cyclic redundancy check (CRC) scrambled usinga group RNTI (G-RNTI).

Aspect 168: The method of Aspect 167, wherein the at least one MBS PDCCHcommunication schedules a plurality of MBS PDSCH communications, whereineach MBS PDSCH communication of the plurality of MBS PDSCHcommunications is associated with a respective group RNTI (G-RNTI) of aplurality of G-RNTIs that includes the G-RNTI.

Aspect 169: The method of Aspect 168, wherein at least one additionalpayload is scrambled according to the PDCCH payload scrambling sequencebased on at least one additional value of the G-RNTI, wherein the atleast one additional value of the G-RNTI is equal to at least oneadditional G-RNTI of the plurality of G-RNTIs.

Aspect 170: The method of either of Aspects 168 or 169, wherein at leastone additional payload is scrambled according to the PDCCH payloadscrambling sequence based on at least one additional value of theG-RNTI, wherein the at least one additional value of the G-RNTI is equalto the value of the G-RNTI.

Aspect 171: The method of any of Aspects 168-170, wherein the value ofthe G-RNTI is equal to a specified G-RNTI of the plurality of G-RNTIs.

Aspect 172: The method of any of Aspects 168-171, wherein the pluralityof G-RNTIs are configured using a G-RNTI list, and wherein the value ofthe G-RNTI is equal to a first listed G-RNTI of the G-RNTI list.

Aspect 173: The method of any of Aspects 168-172, wherein the value ofthe G-RNTI is equal to a G-RNTI mapped to a multicast service.

Aspect 174: The method of Aspect 173, wherein the multicast servicecomprises a specified multicast service ID of a plurality of multicastservice IDs.

Aspect 175: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects163-174.

Aspect 176: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 163-174.

Aspect 177: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 163-174.

Aspect 178: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 163-174.

Aspect 179: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 163-174.

Aspect 180: A method of wireless communication performed by a basestation, comprising: transmitting a multicast/broadcast system (MBS)configuration that indicates a physical downlink control channel (PDCCH)payload scrambling sequence based on a value of a radio networktemporary identifier (RNTI) for a search space associated with aphysical downlink control channel (PDCCH) corresponding to an MBSphysical downlink shared channel (PDSCH), wherein the value of the RNTIis equal to zero; and transmitting at least one MBS PDCCH communicationbased at least in part on the configuration.

Aspect 181: The method of Aspect 180, the method further comprisingtransmitting a configuration of a PDCCH demodulation reference signal(DMRS) scrambling identifier for a control resource set associated withthe search space.

Aspect 182: The method of Aspect 180, wherein the base station does nottransmit a configuration of a PDCCH demodulation reference signal (DMRS)scrambling identifier for a control resource set associated with thesearch space.

Aspect 183: The method of Aspect 180, a PDCCH demodulation referencesignal (DMRS) scrambling identifier is not supported for a controlresource set associated with the search space.

Aspect 184: The method of Aspect 180, wherein the at least one MBS PDCCHcommunication comprises a cyclic redundancy check (CRC) scrambled usinga group RNTI (G-RNTI).

Aspect 185: The method of Aspect 184, wherein the at least one MBS PDCCHcommunication schedules a plurality of MBS PDSCH communications, whereineach MBS PDSCH communication of the plurality of MBS PDSCHcommunications is associated with a respective group RNTI (G-RNTI) of aplurality of G-RNTIs that includes the G-RNTI.

Aspect 186: The method of Aspect 185, wherein at least one additionalpayload is scrambled according to the PDCCH payload scrambling sequencebased on at least one additional value of the G-RNTI, wherein the atleast one additional value of the G-RNTI is equal to at least oneadditional G-RNTI of the plurality of G-RNTIs.

Aspect 187: The method of either of Aspects 185 or 186, wherein at leastone additional payload is scrambled according to the PDCCH payloadscrambling sequence based on at least one additional value of theG-RNTI, wherein the at least one additional value of the G-RNTI is equalto the value of the G-RNTI.

Aspect 188: The method of any of Aspects 185-187, wherein the value ofthe G-RNTI is equal to a specified G-RNTI of the plurality of G-RNTIs.

Aspect 189: The method of any of Aspects 185-188, wherein the pluralityof G-RNTIs are configured using a G-RNTI list, and wherein the value ofthe G-RNTI is equal to a first listed G-RNTI of the G-RNTI list.

Aspect 190: The method of any of Aspects 185-189, wherein the value ofthe G-RNTI is equal to a G-RNTI mapped to a multicast service.

Aspect 191: The method of Aspect 190, wherein the multicast servicecomprises a specified multicast service ID of a plurality of multicastservice IDs.

Aspect 192: An apparatus for wireless communication at a device,comprising a processor; memory coupled with the processor; andinstructions stored in the memory and executable by the processor tocause the apparatus to perform the method of one or more of Aspects180-191.

Aspect 193: A device for wireless communication, comprising a memory andone or more processors coupled to the memory, the one or more processorsconfigured to perform the method of one or more of Aspects 180-191.

Aspect 194: An apparatus for wireless communication, comprising at leastone means for performing the method of one or more of Aspects 180-191.

Aspect 195: A non-transitory computer-readable medium storing code forwireless communication, the code comprising instructions executable by aprocessor to perform the method of one or more of Aspects 180-191.

Aspect 196: A non-transitory computer-readable medium storing a set ofinstructions for wireless communication, the set of instructionscomprising one or more instructions that, when executed by one or moreprocessors of a device, cause the device to perform the method of one ormore of Aspects 180-191.

The foregoing disclosure provides illustration and description but isnot intended to be exhaustive or to limit the aspects to the preciseforms disclosed. Modifications and variations may be made in light ofthe above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construedas hardware and/or a combination of hardware and software. “Software”shall be construed broadly to mean instructions, instruction sets, code,code segments, program code, programs, subprograms, software modules,applications, software applications, software packages, routines,subroutines, objects, executables, threads of execution, procedures,and/or functions, among other examples, whether referred to as software,firmware, middleware, microcode, hardware description language, orotherwise. As used herein, a “processor” is implemented in hardwareand/or a combination of hardware and software. It will be apparent thatsystems and/or methods described herein may be implemented in differentforms of hardware and/or a combination of hardware and software. Theactual specialized control hardware or software code used to implementthese systems and/or methods is not limiting of the aspects. Thus, theoperation and behavior of the systems and/or methods are describedherein without reference to specific software code, since those skilledin the art will understand that software and hardware can be designed toimplement the systems and/or methods based, at least in part, on thedescription herein.

As used herein, “satisfying a threshold” may, depending on the context,refer to a value being greater than the threshold, greater than or equalto the threshold, less than the threshold, less than or equal to thethreshold, equal to the threshold, not equal to the threshold, or thelike.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of various aspects. Many of thesefeatures may be combined in ways not specifically recited in the claimsand/or disclosed in the specification. The disclosure of various aspectsincludes each dependent claim in combination with every other claim inthe claim set. As used herein, a phrase referring to “at least one of” alist of items refers to any combination of those items, including singlemembers. As an example, “at least one of: a, b, or c” is intended tocover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination withmultiples of the same element (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b,a+c+c, b+b, b+b+b, b+b+c, c+c, and c+c+c, or any other ordering of a, b,and c).

No element, act, or instruction used herein should be construed ascritical or essential unless explicitly described as such. Also, as usedherein, the articles “a” and “an” are intended to include one or moreitems and may be used interchangeably with “one or more.” Further, asused herein, the article “the” is intended to include one or more itemsreferenced in connection with the article “the” and may be usedinterchangeably with “the one or more.” Furthermore, as used herein, theterms “set” and “group” are intended to include one or more items andmay be used interchangeably with “one or more.” Where only one item isintended, the phrase “only one” or similar language is used. Also, asused herein, the terms “has,” “have,” “having,” or the like are intendedto be open-ended terms that do not limit an element that they modify(e.g., an element “having” A may also have B). Further, the phrase“based on” is intended to mean “based, at least in part, on” unlessexplicitly stated otherwise. Also, as used herein, the term “or” isintended to be inclusive when used in a series and may be usedinterchangeably with “and/or,” unless explicitly stated otherwise (e.g.,if used in combination with “either” or “only one of”).

What is claimed is:
 1. A user equipment (UE) for wireless communication,comprising: a memory; and one or more processors, coupled to the memory,configured to: monitor a search space associated with a physicaldownlink control channel (PDCCH) corresponding to a multicast/broadcastsystem (MBS) physical downlink shared channel (PDSCH) for at least oneMBS PDCCH communication having a payload that is scrambled according toa PDCCH payload scrambling sequence based on a value of a radio networktemporary identifier (RNTI), wherein the value of the RNTI is equal tozero; and receive the at least one MBS PDCCH communication.
 2. The UE ofclaim 1, wherein the one or more processors are further configured toreceive a configuration of a PDCCH demodulation reference signal (DMRS)scrambling identifier for a control resource set associated with thesearch space.
 3. The UE of claim 1, wherein the UE does not receive aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier for a control resource set associated with the search space.4. The UE of claim 1, a PDCCH demodulation reference signal (DMRS)scrambling identifier is not supported for a control resource setassociated with the search space.
 5. The UE of claim 1, wherein the atleast one MBS PDCCH communication comprises a cyclic redundancy check(CRC) scrambled using a group RNTI (G-RNTI).
 6. The UE of claim 5,wherein the at least one MBS PDCCH communication schedules a pluralityof MBS PDSCH communications, wherein each MBS PDSCH communication of theplurality of MBS PDSCH communications is associated with a respectivegroup RNTI (G-RNTI) of a plurality of G-RNTIs that includes the G-RNTI.7. The UE of claim 6, wherein at least one additional payload isscrambled according to the PDCCH payload scrambling sequence based on atleast one additional value of the G-RNTI, wherein the at least oneadditional value of the G-RNTI is equal to at least one additionalG-RNTI of the plurality of G-RNTIs.
 8. The UE of claim 6, wherein atleast one additional payload is scrambled according to the PDCCH payloadscrambling sequence based on at least one additional value of theG-RNTI, wherein the at least one additional value of the G-RNTI is equalto the value of the G-RNTI.
 9. The UE of claim 6, wherein the value ofthe G-RNTI is equal to a specified G-RNTI of the plurality of G-RNTIs.10. The UE of claim 6, wherein the plurality of G-RNTIs are configuredusing a G-RNTI list, and wherein the value of the G-RNTI is equal to afirst listed G-RNTI of the G-RNTI list.
 11. The UE of claim 6, whereinthe value of the G-RNTI is equal to a G-RNTI mapped to a multicastservice.
 12. The UE of claim 11, wherein the multicast service comprisesa specified multicast service identifier (ID) of a plurality ofmulticast service IDs.
 13. A network node for wireless communication,comprising: a memory; and one or more processors, coupled to the memory,configured to: transmit a multicast/broadcast system (MBS) configurationthat indicates a physical downlink control channel (PDCCH) payloadscrambling sequence based on a value of a radio network temporaryidentifier (RNTI) for a search space associated with a PDCCHcorresponding to an MBS physical downlink shared channel (PDSCH),wherein the value of the RNTI is equal to zero; and transmit at leastone MBS PDCCH communication based at least in part on the configuration.14. The network node of claim 13, wherein the one or more processors arefurther configured to transmit a configuration of a PDCCH demodulationreference signal (DMRS) scrambling identifier for a control resource setassociated with the search space.
 15. The network node of claim 13,wherein the network node does not transmit a configuration of a PDCCHdemodulation reference signal (DMRS) scrambling identifier for a controlresource set associated with the search space.
 16. The network node ofclaim 13, wherein a PDCCH demodulation reference signal (DMRS)scrambling identifier is not supported for a control resource setassociated with the search space.
 17. The network node of claim 13,wherein the at least one MBS PDCCH communication comprises a cyclicredundancy check (CRC) scrambled using a group RNTI (G-RNTI).
 18. Thenetwork node of claim 17, wherein the at least one MBS PDCCHcommunication schedules a plurality of MBS physical downlink sharedchannel (PDSCH) communications, wherein each MBS PDSCH communication ofthe plurality of MBS PDSCH communications is associated with arespective G-RNTI of a plurality of G-RNTIs that includes the G-RNTI.19. The network node of claim 18, wherein at least one additionalpayload is scrambled according to the PDCCH payload scrambling sequencebased on at least one additional value of the G-RNTI, wherein the atleast one additional value of the G-RNTI is equal to at least oneadditional G-RNTI of the plurality of G-RNTIs.
 20. The network node ofclaim 19, wherein at least one additional payload is scrambled accordingto the PDCCH payload scrambling sequence based on at least oneadditional value of the G-RNTI, wherein the at least one additionalvalue of the G-RNTI is equal to the value of the G-RNTI.
 21. The networknode of claim 19, wherein the plurality of G-RNTIs are configured usinga G-RNTI list, and wherein the value of the G-RNTI is equal to a firstlisted G-RNTI of the G-RNTI list.
 22. The network node of claim 19,wherein the G-RNTI is mapped to a multicast service.
 23. The networknode of claim 22, wherein the multicast service comprises a specifiedmulticast service identifier (ID) of a plurality of multicast serviceIDs.
 24. The network node of claim 13, wherein the at least one MBSPDCCH communication comprises a plurality of MBS PDCCH communications.25. A method of wireless communication performed by a user equipment(UE), comprising: monitoring a search space associated with a physicaldownlink control channel (PDCCH) corresponding to a multicast/broadcastsystem (MBS) physical downlink shared channel (PDSCH) for at least oneMBS PDCCH communication having a payload that is scrambled according toa PDCCH payload scrambling sequence based on a value of a radio networktemporary identifier (RNTI), wherein the value of the RNTI is equal tozero; and receiving the at least one MBS PDCCH communication.
 26. Themethod of claim 25, the method further comprising receiving aconfiguration of a PDCCH demodulation reference signal (DMRS) scramblingidentifier for a control resource set associated with the search space.27. The method of claim 25, wherein the at least one MBS PDCCHcommunication comprises a cyclic redundancy check (CRC) scrambled usinga group RNTI (G-RNTI).
 28. A method of wireless communication performedby a network node, comprising: transmitting a multicast/broadcast system(MBS) configuration that indicates a physical downlink control channel(PDCCH) payload scrambling sequence based on a value of a radio networktemporary identifier (RNTI) for a search space associated with a PDCCHcorresponding to an MBS physical downlink shared channel (PDSCH),wherein the value of the RNTI is equal to zero; and transmitting atleast one MBS PDCCH communication based at least in part on theconfiguration.
 29. The method of claim 28, the method further comprisingtransmitting a configuration of a PDCCH demodulation reference signal(DMRS) scrambling identifier for a control resource set associated withthe search space.
 30. The method of claim 28, wherein the at least oneMBS PDCCH communication comprises a cyclic redundancy check (CRC)scrambled using a group RNTI (G-RNTI).